Wendell Piez wrote:
So when text nodes or values of attribute nodes
are constructed (in 2.0), the string-conversion
rules are not followed, but instead all values
are spliced together (with space delimiters, it
appears). This is something to watch out for,
being notably different from 1.0 and potentially
the source of silent bugs when migrating.
Yes. But it is one of the few difference, so when we have to migrate
an XSLT script from 1.0 to 2.0, I think it is one of the thing we have
in mind.
And the incompatibility is only in the cases where we relied in 1.0
on the fact that only the first node of the node-set will be taken,
without write this explicitely (by "[1]"). Which is not a good
practice, IMHO.
Note also that a space delimiter is the default, but statements like
xsl:value-of can set the separator to any string (even empty, which is
usefull), with "@separator". The paragraph I gave the number explains
this simple algorithm (what happens for AVT, xsl:value-of, etcetera).
Regards,
--drkm
___________________________________________________________________________
Faites de Yahoo! votre page d'accueil sur le web pour retrouver directement vos
services préférés : vérifiez vos nouveaux mails, lancez vos recherches et
suivez l'actualité en temps réel.
Rendez-vous sur http://fr.yahoo.com/set
--~------------------------------------------------------------------
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>
--~--