[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

Re: [xsl] Disable output-escaping

Subject: Re: [xsl] Disable output-escaping
From: David Carlisle <davidc@xxxxxxxxx>
Date: Thu, 27 Jan 2005 11:22:56 GMT

   >>>>> "Colin" == Colin Paul Adams <colin@xxxxxxxxxxxxxxxxxx> writes:

       Colin> or equivalently, add a use-character-maps attribute to
       Colin> xsl:value and xsl:text.

   Well, not, it's no quite equivalent, as you can't defining a mapping
   for ASCII NUL to ASCII NUL (for instance) using character maps, as it
   won't pass the XML parser.
   Colin Paul Adams
   Preston Lancashire

well you can't use d-o-e with nulls either as you can't get them into
the data model at all, so the above, while true doesn't really affect

But I'm not sure how you would see a u-c-m attribute on xsl:value and
xsl:text working. a character map already applies to all text in the
result tree including any text generated by these. The whole reason why
character maps are less intrusive than d-o-e is that they apply to the
whole tree so don't need magic properties on individual characters.

Or perhaps you mean that the u-c-m would not be applied at serialisation
time but actually affect the string value of the node generated (ie be
equivalent to using replace() to make all the replacements implied by
the character map, I could have used that. In an application I'm
currently building I have more or less stopped using character maps
and reverted to using template matching as in the rcursive replacement
that Im doing I need the later templates to "see" the new swtrings, know
how long they are, etc, and for that I need to do teh replecements
explictly in xslt not just let the xslt see an identity transfom and
replace teh charcters in a character map at serialisation time.


This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:

Current Thread