Thanks for that, David! I have become so accustomed to using Sarissa
that I sometimes forget what life was like before Manos made this
availlable.
Another +1 for Sarissa (and, of course, for Manos) :D
David Carlisle wrote:
I sort of remember some encoding issues; something about MSXML having
insisting on using UTF-16 for output using certain API bindings.
It does have a preference for utf16 because one of its methods outputs
to some string type thats always utf16 string, but that isn't a
conformance issue: an xslt1 system is explictly allowed to ignore the
encoding hint on xsl:output. A common "problem" people have with msxml
is that they output the whole result as a msxml dom and that dom is then
later serialised by dom serialisation methods (eg .xml), in which case
all of the serialisation is outside xslt's control and xsl:output is
completely ignored. This again is conformant (if confusing) and also
happens with other systems that allow the in-memory result tree to be
passed down some pipeline.
David
________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________
--~------------------------------------------------------------------
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>
--~--
--~------------------------------------------------------------------
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>
--~--