Re: [Freetype] freetype 2.1.2 cmap detection issue <update>

[Phil Morris]

On Wed, Jan 01, 2003 at 02:59:50PM -0700, Phil Morris wrote:
> Hello, This is my first post to freetype and sorry for the long 
> note.
>  
> I'm looking for assistance with an issue I'm having in RH8
> and the Redhat supplied freetype rpms. 
> versions I've tried are the stock 2.1.2-7 and the 2.1.2-12
> rpms from the current phoebe beta. 
> 
> I am running the enlightenment window manager and have been testing
> several of the e cvs packages for the upcoming e17 release. Some of 
> the supplied ttf files in e cvs refuse to render properly using the 
> Redhat freetype rpms. If I remove my 2.1.2 rpms and install 2.0.9 from
> tar.gz then everything works fine. 
> Fonts that don't want to work right include andover.ttf, morpheus.ttf,
> borzoib.ttf and others
> 
> I have tracked the issue down to a problem with cmap detection.
> The issues I am seeing with these fonts are exactly the same as
> discussed in the following email at the end of this note. 
> 
> Can anyone confirm if this is still a known issue with 2.1.2* freetype
> or if there is a patch out there that I would need to apply to 
> the RH src.rpm and rebuild it. 
> 
> Thanks Phil
>
I have tried a recent 2.1.3 tar.gz and the problem seems to have been 
fixed. Now just need to get Redhat to issue 2.1.3 rpms

> <snip>----
> 
>     * To: address@hidden
>     * Subject: Re: FreeType 2.1.2's cmap detection broken?
>     * From: Anthony Fok <address@hidden>
>     * Date: Fri, 9 Aug 2002 18:38:49 +0800
>     * Cc: address@hidden
>     * In-reply-to: <address@hidden>
>     * References: <address@hidden> <address@hidden>
>     * User-agent: Mutt/1.4i
> 
> 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
> 
> _______________________________________________
> Freetype mailing list
> address@hidden
> http://www.freetype.org/mailman/listinfo/freetype