RE: Yet Another Flat File to Hierarchy question..

And convincing MS that it's wrong and that it should be fixed is what I'm
ultimately trying to do!

Bill

 -----Original Message-----
From: 	McNally, David [mailto:David.McNally@xxxxxxxxxx] 
Sent:	Friday, June 14, 2002 1:32 PM
To:	'xsl-list@xxxxxxxxxxxxxxxxxxxxxx'
Subject:	RE:  Yet Another Flat File to Hierarchy question..

You are correct - Xalan worked fine.  I'm sorry I missed your post - which
covers exactly this issue.

Presumably this thread shows that MSXML is not working correctly with
current() in key definitions, and should be fixed...

Thanks,
David.

> -----Original Message-----
> From: Bill Cohagan [mailto:bill.cohagan@xxxxxxxxxxxxx]
> Sent: Friday, June 14, 2002 2:02 PM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: RE:  Yet Another Flat File to Hierarchy question..
> 
> 
> I think the problem you're seeing is related to the problem I 
> described in
> my recent post regarding xsl:key semantics and MSXML. First, 
> a good test
> would be to try your case using Saxon 6.5.2 which appears to 
> "do the right
> thing" with the call to current(), at least for my testcase. I believe
> earlier versions do not. MSXML (any version) does NOT do the 
> right thing as
> far as I can tell. (Xalan may also be a way to test your 
> case. I understand
> that it works properly too.)
> 
> Regards,
>  Bill
> 
>  -----Original Message-----
> From: 	McNally, David [mailto:David.McNally@xxxxxxxxxx] 
> Sent:	Friday, June 14, 2002 12:56 PM
> To:	'xsl-list@xxxxxxxxxxxxxxxxxxxxxx'
> Subject:	RE:  Yet Another Flat File to Hierarchy question..
> 
> For some reason I can't get current() to work in key 
> definitions - or at
> least that seems to be what the problem is.  Using the 
> suggested key below,
> I tried this xslt:
> 
> <snip>
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> 


---------------------------------------

The information contained in this e-mail message, and any attachment
thereto, is confidential and may not be disclosed without our express
permission.  If you are not the intended recipient or an employee or agent
responsible for delivering this message to the intended recipient, you are
hereby notified that you have received this message in error and that any
review, dissemination, distribution or copying of this message, or any
attachment thereto, in whole or in part, is strictly prohibited.  If you
have received this message in error, please immediately notify us by
telephone, fax or e-mail and delete the message and all of its attachments.
Thank you.

Every effort is made to keep our network free from viruses.  You should,
however, review this e-mail message, as well as any attachment thereto, for
viruses.  We take no responsibility and have no liability for any computer
virus which may be transferred via this e-mail message.


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list