Le vendredi 11 mars 2005 Ã 10:01 -0500, Daniel Veillard a Ãcrit : > On Fri, Mar 11, 2005 at 03:49:58PM +0100, Nicolas Mailhot wrote: > > I think the problem here is the changing of document context (but why is > > it affecting keys ? Aren't keys supposed to be more or less stable when > > transformation begins ?) > > no. exslt:tokenize creates a new document. keys() may not be computed > on that document. Unclear if they should be. So you're telling me invoking tokenize on a string to split it up makes xslt loose the current document and all its context ? That would severily limit tokenize usage to leaf processing. I don't want to apply key on anything but the original document - the tokenize is just here so I can look up a variable node number is the source doc using each of the tokens. > > Well it certainly does not work as expected here;( But since I never > > really played with tokenize before, maybe it's my expectations which are > > wrong. > > if your reference a node in the exslt:tokenize result it is in a different > document tree than the current one. > > > Attaching the problem xslt with 4 small xmls to apply on. The command I > > use on it is : > > I honestly don't have much time right now. Do not hold your breath. Hey, sure, I have no right to demand anything of you. If you can spare 30s to look at it, I'd be grateful. My tokenize use is really as simple as what I already posted - the full stylesheet is just here to provide context. Regards, -- Nicolas Mailhot
Attachment:
signature.asc
Description: This is a digitally signed message part