Most XSLT processors allow you to bypass the final stage of serialization,
namely translation of characters into bytes, if you supply a
character-oriented output destination: for example, in Java, a StreamResult
that wraps a StringWriter. You then end up with a sequence of abstract
characters (in Java they will actually be in UTF-16, but you aren't supposed
to care).

Michael Kay
http://www.saxonica.com/ 

> -----Original Message-----
> From: James A. Robinson [mailto:jim.robinson@xxxxxxxxxxxx] 
> Sent: 21 July 2006 20:19
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject:  XSLT default output encoding when method==html?
> 
> 
> I'm writing some code which needs to read the result of an 
> XSLT transformation into a string.  The XSLT specification 
> clearly states what a processor is supposed to do if the 
> output method is xml, xhtml, or text, but no output encoding 
> is specified, which is great.
> 
> I'm unable to figure out if it says somewhere what occurs if 
> html is the output method and no encoding is specified.  
> Anyone able to point me at the right information?  Or does 
> this end up being 'processor specific' ?
> 
> 
> Jim
> 
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> James A. Robinson                       jim.robinson@xxxxxxxxxxxx
> Stanford University HighWire Press      http://highwire.stanford.edu/
> +1 650 7237294 (Work)                   +1 650 7259335 (Fax)