This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: AW: Problem parsing cp1252 with msxsl > UTF-8 ?
- From: Mike Brown <mike at skew dot org>
- To: xsl-list at lists dot mulberrytech dot com
- Date: Fri, 14 Jun 2002 11:34:19 -0600 (MDT)
- Subject: Re: AW: [xsl] Problem parsing cp1252 with msxsl > UTF-8 ?
- Reply-to: xsl-list at lists dot mulberrytech dot com
bryan wrote:
> 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.
Even that doesn't work sometimes. It depends on how you invoke the
transformation. This message from Andy Kimball explains:
http://www.biglist.com/lists/xsl-list/archives/200108/msg00541.html
- Mike
____________________________________________________________________________
mike j. brown | xml/xslt: http://skew.org/xml/
denver/boulder, colorado, usa | resume: http://skew.org/~mike/resume/
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list