This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Xalan Vs. Output Escaping
- From: Matthew Jaquish <mjaquish at cisco dot com>
- To: XSL-List at lists dot mulberrytech dot com
- Cc: Jan Borgersen <Jan dot borgersen at razorfish dot com>
- Date: Wed, 23 Jan 2002 11:41:56 -0800
- Subject: [xsl] Xalan Vs. Output Escaping
- Reply-to: xsl-list at lists dot mulberrytech dot com
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" : ..... & ... & ... %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,
...Matt
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list