Altova Mailing List Archives

RE: [xsl] FW: ] Top Ten Java and XSLT Tips, #5

From: "Julian Reschke" <julian.reschke@------>
Date: 9/5/2001 1:45:00 AM
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Chris Bayes
> Sent: Wednesday, September 05, 2001 11:15 AM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: RE: [xsl] FW: ] Top Ten Java and XSLT Tips, #5
> Hi David,
> > that's what you see if you look at the utf8 encoding of the
> > character in a latin1 encoded window.
> >
> > IE5 on windows will only do that if you set it up wrong:
> > forcing it to use the latin1 encoding even if the document
> > specifies utf8.
> >
> > Much as I'd prefer to blame microsoft I suspect user error in
> > this case.
> It doesn't work on IE6 final either. At least the final I have here. It
> displays &#160; as A^  AND for some reason all of the encodings are
> greyed out and the only one available is western encoding (windows).
> In fact there are so many bugs in IE6 I am surprised it was released.
> That doesn't mean to say I agree with tip #5 as IE6 has only been out a
> week.

I don't agree that IE is to be blamed.

What's happening is that XHTML/XML is loaded into a browser with "html" file
extension, which (AFAIK) IE will treat as if the content-type would have
been "text/html". Don't expect him to do any XML-ish thing with it.

 XSL-List info and archive:


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.