This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: AW: Problem parsing cp1252 with msxsl > UTF-8 ?
- From: "bryan" <bry at itnisk dot com>
- To: <xsl-list at lists dot mulberrytech dot com>
- Date: Fri, 14 Jun 2002 10:39:17 +0200
- Subject: RE: AW: [xsl] Problem parsing cp1252 with msxsl > UTF-8 ?
- Reply-to: xsl-list at lists dot mulberrytech dot com
>Solution:
>get a smarter text editor that lets you choose the encoding to save
files
>with.
Yeah, even Notepad on Windows 2000 lets you save as UTF-8 nowadays. :)
By the way I'm probably off here but I haven't been following the thread
and it seems from the subject that there's a problem associated with
msxsl(the command line xsl-t processor from Microsoft) specifically and
UTF-8 encoding, I've noted that msxsl tends to output UTF-16, at least
I've had situations were it did despite all my encodings in my source
and transform documents being UTF-8; however if you have an <xsl:output
method="xml" encoding="UTF-8"/> everything goes as it should.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list