Re: Character encoding problem

David Carlisle writes:
 > 
 >   <xsl:output method="html" encoding="$charEncoding"/>
 > 
 > you can't do that: you have to fix the output encoding.

Dohh!

Then maybe I could include a stylesheet for English or Japanese? You
don't have to answer that -- I'll look it up in the bible.

Michael Kay writes:
 > > Saxon:
 > > 	$ saxon main.html i18n.xsl currentLanguage=en
 > > 	Transform failed: =US-ASCII
 > 
 > The leading "=" suggests you're hitting bug 6.2.2/010; but I've no idea why.

Actually, I'm using Saxon 6.02. Time to upgrade once again, eh?

 > This bug suggests that the input is being read from a source that has
 > external encoding information associated with it, typically an HTTP header.

There shouldn't be any of those involved. It's just a local file.

Thank you, gentlemen.


Matt Gushee

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list