This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Unicode usage


[Julian Reschke]

> > >
> >
> > "Accept" settings aren't the same as display settings.  Normally,
> > Microsoft
> > products (i.e., Windows) display using a Microsoft character set,
> > the famous
> > codepage 1252 (I think that's the one).  So you may well have the
correct
> > unicode character, but it will be displayed according to the codepage.
If
> > the codepage doesn't have characters for them, it will show empty boxes.
>
> I think this is a misunderstanding. If the encoding is properly declared,
> but the characters are displayed as empty boxes, this is likely cause by
the
> fact that the font which is used for display just doesn't have character
> glyphs at these positions.
>

Maybe there's a misunderstanding, but I think we're pretty close.  We agree
that if the display font doesn't have a glyph for a character, you will get
and empty box.  You are saying, I think, that if the encoding is declared to
be UTF-8, for instance, the browser or the editor or whatever should
translate that to the corresponding character in the display character set
and thence display it correctly.

That would seem logical, but I don't think it always happens.  I think it
depends on the version of Windows you have and which application you use.
Just think of all those posts to this list where an accented character
displayed as something else.  We usually tell them that the character is
correct in the file but not displayed right because of the encoding - there
must be dozens of posts like that.

If I remember what people have said, on Win95/98,  for instance, Notepad
doesn't know about utf-8, whereas on Win2000, Notepad is supposed to know
about it.

> >
> > Maybe someone else knows a solution for this problem of displaying
> > high-order characters...
>
> I don't think this is a general problem at all. Just refer to the
> appropriate Unicode character code, and then it's up to the browser to
find
> a way to display th character.
>

Ideally, but if your browser/OS combination doesn't do that, what then?

Cheers,

Tom P


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]