Re: [Devel] Re: FreeType 2.1.2's cmap detection broken?

[jonathan . foster]

Hi,

I had problems rendering Tiresias.ttf after upgrading from 2.0.9 to 2.1.1.  
Turning off FT_CONFIG_OPTION_USE_CMAPS fixed it, however it looks like this 
option has been removed from the CVS version of FT2.

Kind regards,

Jon Foster

Anthony Fok <address@hidden> wrote:

Hello David and all,

About a month ago, a user/developer reported here that opens___.ttf
could no longer be displayed in OpenOffice.org.  Since then, there have
been similar reports by different Debian users reporting problems since
the upgrade from libfreetype6-2.0.9 to 2.1.x.  And then yesterday
Guillermo Perez noticed that ftdump1 shows more cmaps than ftdump2
does.

With that, it appears that a real bug may have crept in between 2.0.9
and 2.1.0+.  With opens___.ttf font, ftdump from FreeType pre-1.4 reports:

             encoding  0: Apple Unicode
             encoding  1: Apple Roman
             encoding  2: Windows Unicode

ftdump from FreeType 2.0.9 reports:

             charmaps
                0: platform: 0, encoding: 0
                1: platform: 1, encoding: 0
                2: platform: 3, encoding: 1

fonttools reports:

    <cmap_format_4 platformID="0" platEncID="0" version="0">
    <cmap_format_6 platformID="1" platEncID="0" version="0">
    <cmap_format_4 platformID="3" platEncID="1" version="0">

ftdump from FreeType 2.1.2 (with CVS as of 2002-08-06) reports:

             charmaps
                0: platform: 1, encoding: 0   <--- Only one left!?!

Apparently, this is the cause of a recent font display problem for
e.g. some OpenOffice.org and pango users.
http://www.usta.de/RefAk/Aussen/almonte.ttf is another font that triggers
the symptom.

For more information, please check:

    freetype regression: some ttf fonts don't display anymore
        http://bugs.debian.org/150678

    some fonts are not rendered because their enconding are not well detected
             http://bugs.debian.org/155864

Many thanks,

Anthony

On Wed, Jul 10, 2002 at 07:32:43PM +0200, David Turner wrote:
> Pavel Jan?k wrote:
> >Hi,
> >
> >I'm currently working on upgrading build-in freetype in
> >OpenOffice.org. I successfully upgraded to 2.0.9. Now I'm trying to go to
> >2.1.0, but I have reached the problem with one font - it is known as
> >OpenSymbol in OpenOffice.org (you can find it in
> >OpenOffice.org1.0/share/fonts/truetype/opens___.ttf if you installed OOo,
> >or in extras/source/truetype/symbol/opens___.ttf if you have
> >sources. I have also uploaded it to http://www.janik.cz/tmp/opens___.ttf
> >for your convenience). It is not rastered as it was in 2.0.9. I have asked
> >Pavel Ka?kovsk? about that issue and he told me to try 2.1.2. I did so, but
> >the result is the same as it was with 2.1.0 so we are at 2.0.9 right
> >now. And this is also the reason of this letter ;-)
> >
> >This problem is most easily reproduced via Insert -> Special symbol
> >OpenOffice.org menu. I have created two screenshots of the Special Symbols
> >dialog with OpenSymbol font. The first one is with freetype 2.0.9, the
> >second one is with 2.1.2. With 2.1.2, no character is rasterized. I think
> >this is clearly the bug in the font itself or in 2.1.2. I think you can be
> >interested in solving the problem.
> >
> >The problem can be seen with or without byte code interpreter and I use the
> >appended patches to build OOo with the newest freetype:
> >
> >freetype-2.1.2.patch - this patch is only updated from built-in 2.0.5 and
> >the only difference is byte code interpreter turned on
> >
> >OO-new-freetype-patch.diff - you have changed NEXT_UShort to FT_UShort and
> >similar
>
> Hello,
>
> Why are you using FT_UShort, which is a **type** ??
> You should be using "FT_NEXT_USHORT" instead of "NEXT_UShort"
>
> Note that I don't have a problem displaying the font with "ftview" and
> 2.1.2,
> and ftdump only reports an Apple Roman charmap (no Unicode)
>
> Hope this helps,