This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: Top Ten Java and XSLT Tips, #5
- To: <xsl-list at lists dot mulberrytech dot com>
- Subject: RE: [xsl] Top Ten Java and XSLT Tips, #5
- From: "Julian Reschke" <julian dot reschke at gmx dot de>
- Date: Sat, 1 Sep 2001 08:05:43 +0200
- Reply-To: xsl-list at lists dot mulberrytech dot com
> From: owner-xsl-list@lists.mulberrytech.com
> [mailto:owner-xsl-list@lists.mulberrytech.com]On Behalf Of Benjamin
> Franz
> Sent: Friday, August 31, 2001 7:35 PM
> To: xsl-list@lists.mulberrytech.com
> Subject: RE: [xsl] Top Ten Java and XSLT Tips, #5
>
>
> On Fri, 31 Aug 2001, Julian Reschke wrote:
>
> >
> > I'd have less problems with "good advice" like that if somebody
> could give a
> > real-world example where   doesn't work properly.
>
> The problem is with default character sets. If a browser doesn't use
> either UTF8 or an ISO-8859-x encoding for its default, high bit characters
> sometimes turn into either '?' or other nonsensical things. It is a very
> common problem for non-latin character set people (especially for those
> like Japanese having multi-byte encodings).
>
> By generating an explicit entity rather than getting an inlined character
> the problem doesn't appear so much (at least not in new browsers).
So which "new" browsers *are* affected? Surely not Netscape >6, IE >5 or
Mozilla, right?
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list