RE:   doesn't work for some browsers

I had a similar problem it would show up as an accented 'A' when going through 
some parsers.

If you have not already figured out a solution I realized it was because my 
transform inputs were XML (UTF8) and XSL (UTF8), which would work with XML Spy 
but when I would send it through my .NET code for XSL Transform it would come 
out as HTML (UTF-16).

So I locked it down to ensure that the output was also UTF-8. Poof :) Worked.

You can do this 2 ways:
1. By adding this attribute to ensure UTF-8 <xsl:output encoding="UTF-8">
2. By adding encoding inside the code used to invoke the sheets (.NET in my 
case). 

System.Text.Encoding.UTF8
Or
System.Text.UTF8Encoding

Hope that helps.

Regards,

Abhishek Sanwal
HP - Houston Campus
abhishek(_dot_)sanwal(_at_)hp(_dot_)com

-----Original Message-----
From: Weaver, Debbie [mailto:debbie(_dot_)weaver(_at_)hants(_dot_)gov(_dot_)uk] 
Sent: Thursday, October 09, 2003 6:15 AM
To: XSL-List(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: [xsl]   doesn't work for some browsers

Hello,

I've been happily using &#160; in my XSL stylesheets for a while now but have 
recently come across a problem where in some browsers the output is either 
displayed as a ? or a box.

I understand that this is probably due to the browser misinterpreting the 
character encoding, but my question is - how can I get around this problem?  I 
have substituted &#160; for &#32; and that does seem to solve the problem, but 
to be honest...I'm not really sure why or whether it is an OK solution.

I hope someone can help,

Thanks--- Debbie



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


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