freefont-bugs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Freefont-bugs] OS/2 tables


From: Primoz PETERLIN
Subject: Re: [Freefont-bugs] OS/2 tables
Date: Wed, 7 May 2003 18:48:01 +0200 (METDST)

-----BEGIN PGP SIGNED MESSAGE-----

On Tue, 6 May 2003, Josef W. Segur wrote:

> > What could then be the reason that Internet Explorer doesn't offer
> > FreeMono as a Greek font? The CodePageRange table for FreeMono reads
> > "800000bf 00000000", which I interpret as covering Latin 1, Latin 2,
> > Cyrillic, Greek, Turkish, Hebrew, Windows Baltic and Symbol Character Set
> > pages.
>
> The problem may be caused by that "Symbol Character Set" bit being
> set. I do run Win95 but don't have Internet Explorer, so I can't
> actually check.
> That flag bit is meant for fonts with arbitrary non-Unicode glyphs,
> such as WingDings and WebDings. I suggest clearing it for
> FreeMono.ttf, FreeSans.ttf, and FreeSerif.ttf. The italic, bold, and
> other variants are OK already.

Is it? I thought that the bit should be set if the fonts contains glyphs
from the set of Microsoft "symbol" font. At least both Symbol and
Wingdings fonts have this bit set, while, say, Times and Tahoma do not:

symbol.ttf               CodePageRange=80000000 00000000
tahoma.ttf               CodePageRange=2000009f 00000000
tahomabd.ttf             CodePageRange=2000009f 00000000
times.ttf                CodePageRange=400001ff ffff0000
timesbd.ttf              CodePageRange=400001ff ffff0000
timesbi.ttf              CodePageRange=400001bf dff70000
timesi.ttf               CodePageRange=400001bf dff70000
wingding.ttf             CodePageRange=80000000 00000000

FreeMono.ttf, FreeSans.ttf, and FreeSerif.ttf indeed contain "symbol"
characters; the italic, bold and bold italic variants currently don't (and
there is little point having, say, slanted box-drawing characters :) So I
believe these fonts should have the "Symbol Character Set" bit set. My
concern is that Microsoft have set numerous other bits as well (mostly
referring to the MS-DOS code pages) which are not set in the Free fonts,
and this might be the culprit.

It bothers me, though, why IE should rely on the old MS-DOS code pages.

With kind regards,
Primoz

- --
Primož Peterlin,   Inštitut za biofiziko, Med. fakulteta, Univerza v Ljubljani
Lipičeva 2, SI-1000 Ljubljana, Slovenija.  address@hidden
Tel +386-1-5437632, fax +386-1-4315127,  http://biofiz.mf.uni-lj.si/~peterlin/
F8021D69 OpenPGP fingerprint: CB 6F F1 EE D9 67 E0 2F  0B 59 AF 0D 79 56 19 0F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (HP-UX)
Comment: For info see http://www.gnupg.org

iQB1AwUBPrk4xT3bcxr4Ah1pAQE7kAMAkHwyCVT+r5KBVRTh59tb2pPJNM6Q4cyC
MkVrd8iv84g4+Lv+aDcFQKsM/CGqa2Nzx/ypNGzG/K8YAVbrWNlU4R1FLVFz5eQ+
8Drj1BLwhXRrQdpDqTXXV7gzIFM/AoFv
=Oudn
-----END PGP SIGNATURE-----





reply via email to

[Prev in Thread] Current Thread [Next in Thread]