-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jan Willem Stumpel wrote:
> Arne Götje (高盛華) wrote:
>> [..] yes, it depends totally on the font to define the
>> *position* of the accents (and weather or not they can be
>> stacked). But it depends on the rendering engine to *interpret*
>> the information the font gives about the accents.
>>
>> BTW: there was no irony in my statement. In Fontforge it is
>> really easy to define the "anchors". For all pre-composed Latin
>> based combinations, you can get it done with around 10 anchor
>> classes, including the stacked ones for Vietnamese.
>
> Is it also easy to create a GPOS table for a font which does not
> have one? My experience with Fontforge is very limited!
As soon as any GPOS feature ("anchors" is one if the features) is
present, the table is created automatically.
> In the meantime I found that most fonts on my system do *not* have
> this table (including the Bitstream Vera fonts and the MS "core"
> fonts). It seems that including such a table is one of the things
> that we must "badger" upstream font developers about.
Exactly.
>> [..] Example: o <U+0301> <U+0358> -> ó͘
>
> This example displays OK on my system with your uming.ttf font
> (naturally), but also (by "luck") with, for instance, Bitstream
> Vera Serif (which does not have the combining accent characters,
> nor a GPOS table). I suppose the rendering engine (pango) borrows
> the accents from another font (yours, probably). But how can it
> know where to place them? The base characters in Bitstream Vera
> Serif do not have anchors.
This also puzzles me. but the glyphs do not come from my font, they look
different... I'd have to take a closer look on the fonts if I find some
time... I assume that if there are no GPOS information present, pango
and other rendering engines classify the combining accents by unicode
coderange and just center them over the preceding (latin) character...
(maybe someone of the pango guys can answer this...?)
Cheers
Arne
- --
Arne Götje (高盛華) <[EMAIL PROTECTED]>
PGP/GnuPG key: 1024D/685D1E8C
Fingerprint: 2056 F6B7 DEA8 B478 311F 1C34 6E9F D06E 685D 1E8C
Key available at wwwkeys.pgp.net. Encrypted e-mail preferred.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFfS5Ybp/QbmhdHowRApPWAJsESNwk1M29ngc8op6Uf1RRJVnDBwCgmEOR
grh/GERXv0DrzsqXj+ousV8=
=m8wc
-----END PGP SIGNATURE-----
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
