Subject: RE: [xsl] Top Ten Java and XSLT Tips, #5 From: "Julian Reschke" <julian.reschke@xxxxxx> Date: Sat, 1 Sep 2001 08:05:43 +0200 |
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx > [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Benjamin > Franz > Sent: Friday, August 31, 2001 7:35 PM > To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx > 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
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Re: javascript & XSL, Mike Brown | Thread | [xsl] xslt svg problem, Max Nitribitt |
[xsl] Re: javascript & XSL, Dimitre Novatchev | Date | [xsl] xslt svg problem, Max Nitribitt |
Month |