Altova Mailing List Archives

[xsl] Xalan Vs. Output Escaping

From: Matthew Jaquish <mjaquish@--------->
Date: 1/23/2002 9:37:00 AM
Hello fellow intrepid XSL adventurers,

My team was recently quite aggravated by a possible bug (or feature?) in Xalan's output escaping. We were using output encoding="html", and the values we were comparing were "&" and "%3A". We were seeing unanticipated results among the various methods of getting a value.

Let's watch the translation of characters in Xalan (doe = disable-output-escaping):

XML Source        :  ..... & ....... & ....... %3A .....
value-of doe="no" :  ..... &amp; ... &amp; ... %3A .....
value-of doe="yes":  ..... & ....... & ....... %3A .....
curly braces {}   :  ..... & ....... & ....... %253A ...

According to this, doesn't it seem that using curly braces should give us the same value as either of the value-of methods? Why are the curly braces give a totally different value for the "%3A" value? Am I missing something here about the behavior of curly braces, or is there a bug in Xalan that I was unaware of? Hopefully this will also help other people using Xalan, as well.

I appreciate your insight,


 XSL-List info and archive:


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.