[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Fw: Re: [ft] opentype problems
From: |
mpsuzuki |
Subject: |
Re: Fw: Re: [ft] opentype problems |
Date: |
Wed, 27 Apr 2005 09:13:35 +0900 |
On Tue, 26 Apr 2005 21:15:25 +0900
address@hidden wrote:
>I modified the value by binary editor. (It's lucky that freetype can
>load the font file with wrong checksum :-))
>
>00000000 00 01 00 00 00 14 01 00 00 04 00 40 47 44 45 46 address@hidden
> [snip]
>000000D0 9C 84 04 5E 00 00 01 4C 00 00 00 36 68 68 65 61 ...^...L...6hhea
>000000E0 06 D3 FD 6C 00 00 01 84 00 00 00 24 68 6D 74 78 ...l.......$hmtx
> ^^^^^^^^^^^ (hhea starts 0x00000184)
> [snip]
>00000180 00 00 00 00|00 01 00 00|02 F8|FF 37|00 3B|FF FF ...........7.;..
> | version | xxx | xxx | xxx |<HERE>
>
>When I decrease 0xFFFF to smaller values, the glyph width gets
>smaller, but the rendering result of old ftview (including
>wrong glyph width bug) is still different from current ftview.
>See attached picture, I suppose Burmese ligature functionalities
>are broken.
Just I've checked how modified yngn.otf of decreased-advanceWidthMax
works with FireFox, and confirmed that OpenType functionalities for
Burmese script are broken. Furturemore, it seems that all glyphs
(both of US-ASCII glyphs and Burmese glyphs) are layouted aslike if
they were "fixed-width". Oops.
Regards,
mpsuzuki
- Re: [ft] opentype problems, (continued)
- Re: [ft] opentype problems, pabs, 2005/04/25
- Re: [ft] opentype problems, Werner LEMBERG, 2005/04/25
- Re: [ft] opentype problems, mpsuzuki, 2005/04/26
- Re: [ft] opentype problems, Werner LEMBERG, 2005/04/26
- Re: [ft] opentype problems, mpsuzuki, 2005/04/26
- Re: [ft] opentype problems, pabs, 2005/04/26
- Re: [ft] opentype problems, mpsuzuki, 2005/04/26
- Re: [ft] opentype problems, pabs, 2005/04/26
- Re: [ft] opentype problems, Werner LEMBERG, 2005/04/27
Fw: Re: [ft] opentype problems, mpsuzuki, 2005/04/26
- Re: Fw: Re: [ft] opentype problems,
mpsuzuki <=