Hi Micheal,
That was with the XmlTextWriter output stream, which is a layer on top of
the raw output stream. The documentation for XmlTextWriter stated that it
has that behaviour, but it appears that it's in the processor not this
special output stream. I'm now bypassing this and getting the raw byte[]
output from the XslTranslator, but it appears that the problem is really in
the translator.
Yes, it's a pity that the processor that comes standard with .NET is buggy
in this way.
Regards,
Steven
-----Original Message-----
From: Michael Kay [mailto:mhk(_at_)mhk(_dot_)me(_dot_)uk]
Sent: Thursday, 20 May 2004 1:12 AM
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: RE: [xsl] Is it possible to get " " in output rather than the
encoded character?
The three results show that the encoding is being considered, but for
us-ascii the output is broken. What I'm expecting is that the
processor should be smart enough to use the � notation for
extended ascii characters when in us-ascii mode. Maybe I'm expecting
too much.
I thought you already told us you had found documentation that explained
this behavior. Which doesn't make it any better. Sounds like you need a
different XSLT processor - fortunately there are plenty to choose from.
Michael Kay
--+------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--+--