This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: a special char question
- To: Selim Cesic <Selim dot Cesic at synes dot com>
- Subject: RE: a special char question
- From: John Robert Gardner <jrgardn at emory dot edu>
- Date: Fri, 23 Jun 2000 10:44:01 -0400 (EDT)
- cc: xsl-list at mulberrytech dot com
- Reply-To: xsl-list at mulberrytech dot com
I'm not certain what you are _trying_ to get, but double-escaping is
another option . . . though as I read this, I'm not sure if it applies . .
. this is the kind of question Derrida or a deconstructionist would really
dig . . .
If you wanted "<" to be read in the browser looking like that, you'd
have to double-escape prior to XSLT processing: &lt;
THis would display as "<" in the browser after XSLT processing. No
disabling of output escaping voodoo needed.
If you think that, in general, if you want to _see_ <, >, ', ", or & -- in
other words, have them in your human-readable text looking like that, you
_would_ disable output escaping.
jr
=-=-=-=-=-=-=-=-=-=-=-=-=-
John Robert Gardner, Ph.D.
XML Engineer
---------------------------------------------------------------
http://vedavid.org/diss/
http://vedavid.org/xml/
You already have zero privacy --
Get over it.
-Scott McNeally
On Fri, 23 Jun 2000, Selim Cesic wrote:
>
> <!>I can't see why you're using disable-output-escaping. This is
> <!>for use when
> <!>you want special characters such as "<" in text to be
> <!>interpreted as markup,
> <!>the default action is to treat them as character data, which is what you
> <!>want.
>
> okay, i've removed disable-output-escaping, result is the same:
>
>
> Fri Jun 23 08:40:40 GMT+02:00 2000 <
> Fri Jun 23 08:40:40 GMT+02:00 2000 >
> Fri Jun 23 08:40:40 GMT+02:00 2000 &
> Fri Jun 23 08:40:40 GMT+02:00 2000 <6162
> Fri Jun 23 08:40:40 GMT+02:00 2000 <66
> Fri Jun 23 08:40:40 GMT+02:00 2000 >70
>
>
>
> HTML code (outputed from processor) looks like:
>
> <TR bgcolor="#008000">
> <TD><FONT SIZE="2"><b>Fri Jun 23 11:56:46 GMT+02:00 2000</b></FONT></TD>
> <TD><FONT SIZE="2"><b><</b></FONT></TD>
> </TR>
> <TR bgcolor="#008000">
> <TD><FONT SIZE="2"><b>Fri Jun 23 11:56:46 GMT+02:00 2000</b></FONT></TD>
> <TD><FONT SIZE="2"><b>></b></FONT></TD>
> </TR>
> <TR bgcolor="#008000">
> <TD><FONT SIZE="2"><b>Fri Jun 23 11:56:46 GMT+02:00 2000</b></FONT></TD>
> <TD><FONT SIZE="2"><b>&</b></FONT></TD>
> </TR>
> <TR bgcolor="#008000">
> <TD><FONT SIZE="2"><b>Fri Jun 23 11:56:46 GMT+02:00 2000</b></FONT></TD>
> <TD><FONT SIZE="2"><b><6162</b></FONT></TD>
> </TR>
> <TR bgcolor="#008000">
> <TD><FONT SIZE="2"><b>Fri Jun 23 11:56:46 GMT+02:00 2000</b></FONT></TD>
> <TD><FONT SIZE="2"><b><66</b></FONT></TD>
> </TR>
> <TR bgcolor="#008000">
> <TD><FONT SIZE="2"><b>Fri Jun 23 11:56:46 GMT+02:00 2000</b></FONT></TD>
> <TD><FONT SIZE="2"><b>>70</b></FONT></TD>
> </TR>
>
>
> so this can't be a browser problem......
>
> what am i doing wrong?
>
> thx
>
> -SeJo
>
>
>
> <!>
> <!>Telling us what your browser shows isn't very useful; it's the generated
> <!>HTML that's interesting. I suspect the generated HTML is "<&>" and the
> <!>browser is trying its best to make sense of it, which it isn't doing very
> <!>successfully. What you want to generate is "<&>"
> <!>
> <!>Mike Kay
> <!>
> <!>
> <!> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
> <!>
>
>
> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
>
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list