Re: [Devel] Fix for PFR glyph index problem

[Sven Neumann]

Hi,

myself <address@hidden> wrote:

> Anthony Fok <address@hidden> writes:
> 
> > I wonder if it is related to the same changes in FreeType 2.1.1: After
> > upgrading FreeType 2.1.1, Nautilus is no longer able to display
> > anti-aliased fonts under the icons.  It appears that librsvg1
> > (SAX-based renderer library for SVG files) is responsible for calling
> > FreeType to render the fonts; it works with TrueType fonts, but not
> > with Type 1 fonts
> 
> I'm observing similar problems since upgrading to 2.1.1. PangoFT2
> stopped to list a number of my TrueType fonts and even though I can
> access these font files with gimp-freetype as well as with DirectFB,
> they both render nothing but the unknown glyph for whatever character
> index :-(

I've investigated further and it seems that FT_CONFIG_OPTION_USE_CMAPS
causes the offending fonts to be rejected. It's probably time to ditch
those crappy fonts we use and switch to proper ones...


Salut, Sven