RE: [xsl] Encoding problem !!

Subject: RE: [xsl] Encoding problem !!
From: "SANWAL, ABHISHEK (HP-Houston)" <abhishek.sanwal@xxxxxx>
Date: Thu, 16 Oct 2003 19:46:26 -0500
I spent around a week on a similar issue. Of course I could not post it
here as it was a .NET MS specific issue not related EXACTLY to W3C-XSL
but nuances of parsers/xsl transformers. (Is that allowed here)

The Xml/Xsl, Text.Encoding and String & MemoryStream objects under .NET
have certain peculiarities where when I start with a UTF-8 document
(using XMLSpy for development) and translate I get a UTF-8 HTML.

When I run it through the .NET code the output is UTF-16.
Then when I reload some XML using string objects it is again UTF-16.

So I tried to enforce UTF-8 everywhere and had some luck and then had
more issues as listed below.

Some of the objects you cannot re-define or specify an ENODING
ie. The Encoding property is read-only. WHY? GO figure.

I did the same as the link and ensure that everything was UTF-8.

I hope that helps.

Abhishek Sanwal
HP - Houston Campus

-----Original Message-----
From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
[mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Dipesh
Sent: Thursday, October 16, 2003 9:49 AM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: [xsl] Encoding problem !!


I am having one xsl in which I have mentioned the ouput format as

<xsl:output method="text" encoding="ISO-8859-1"/>

When i ran my input file using msxsl processor it gave me error like
"Unable to save character to ISO-8859-1 encoding.

When i ran the same on the processor used by XML Spy it worked well and
me output without error.

Which type of character will be most efficently used across cross

Can someone please throw lights on this issue. 
Thanks in the anticipation that i will get chance to increase my
knowledge in 
this area.


 XSL-List info and archive:

 XSL-List info and archive:

Current Thread