Re: Character 150 withs Windows-1252 output
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)
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format