RE: Non-ASCII Font name behavior in IE

Jungshik,

If it does work on Win9x/ME, then call that a bonus, because it was not a supported feature.

Regards, Russ (rrolfe)
One of the World-Ready Guides (wrg)
Are you World-Ready?  http://www.microsoft.com/globaldev


 

-----Original Message-----
From: public-i18n-geo-request@w3.org [mailto:public-i18n-geo-request@w3.org] On Behalf Of Jungshik Shin
Sent: Thursday, March 18, 2004 9:07 PM
To: public-i18n-geo@w3.org
Subject: Re: Non-Latin Font name behavior in IE



Hi,

> Windows 2000 and later processes the Asian (non-Latin) native font 
> names the same way as the Latin font name. It is just a function of 
> the OS and not a function of IE. Of course this means that it does not 
> work on Win9x.

  Did you actually test that on Win 9x/ME? I also thought it wouldn't work on Win 9x/ME, but it might just work because some 'W' APIs on Win 9x/ME are 'natively' supported (although font-enum APIs are not likely to be among those).  See <http://bugzilla.mozilla.org/show_bug.cgi?id=231426>
for a mozilla bug on the issue.

  BTW, it'd better to say 'non-ASCII' (instead of non-Latin) because the only ASCII part is common in all Windows code pages.

 Anyway, it's not a good idea to list only native font names in CSS because some OS'/browsers  cannot recognize native font names. They always have to be followed by the corresponding ASCII-only names.

 Jungshik