David Carlisle escribió:
Thanks Mukul (and Aron), this works for me. However, doesn't this method
mean that after the main <html>...</html> is formed, it is read again to
parse the TD element change?
isn't there a more efficient way which
makes the copy in one scan of the XML contents instead of two?
The processing model for xslt isn't specified, only the effective
results, so any construct may in prnciple cause any number of scans, but
in practice all XSLT processors only parse the input once, and generate
an input tree over which the entire stylesheet then has read access.
The solutions specified are the standard idiom for writing xslt
stylesheets and it's most likely that the processor's template matching
is optimised to handle constructs like this. (Actually I'm not sure
where you think that the proposed code would lead to two scans)
David
Thanks David. Now I know a little bit more about XSLT :D
Thanks also to Aron and Mukul. I like this list.
Regards,
knocte
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--