Subject: [xsl] Re: Character 150 withs Windows-1252 output From: "andrew welch" <andrew.j.welch@xxxxxxxxx> Date: Thu, 20 Apr 2006 18:41:22 +0100 |
Reading around a bit 150 is a control character... so does that mean it shouldn't appear in source XML document (unresolved) where the encoding is specified as ISO-8859-1 ?? On 4/20/06, andrew welch <andrew.j.welch@xxxxxxxxx> wrote: > Why is it that #150 gets escaped when using Windows-1252 output > encoding when it should contain that character? > > <xsl:stylesheet version="1.0" > xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> > <xsl:output encoding="Windows-1252" method="xml"/> > <xsl:template match="/"> > <html> > <head></head> > <body>–</body> > </html> > </xsl:template> > </xsl:stylesheet> > > This produces the output <body>&_#150;</body> - I would have expected > the character to be resolved... > > (using msxml and saxon 6.5.4, 8.7.1)
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] Character 150 withs Windows-1, andrew welch | Thread | RE: [xsl] Re: Character 150 withs W, Michael Kay |
[xsl] Character 150 withs Windows-1, andrew welch | Date | RE: [xsl] Character 150 withs Windo, XSLList |
Month |