Re: [ft-devel] problems with OpenType/CFF in Freetype 2.3.0

[David Turner]

Hello Axel,

the CFF loader was partly rewritten to strongly reduce its heap usage,
it may be possible that a subtle bug lurked in. Could you send me and
Werner the fonts privately, I'll see what I can do.

Regards,

- David

On Wed, 24 Jan 2007 16:52:59 +0100, "Axel Stoltenberg" <address@hidden> said:
> Hello list,
> 
> since we updated to FreeType 2.3.0, some glyphs in
> some of our fonts (Opentype, CFF) are not rendered any more.
> 
> My sample font was generated from Type1 to OpenType with Adobe's SDK.
> 
> If I use our own fontdisplayer (which uses FreeType) or Freetype's demo
> program
> "ftstring", several characters (i, j, m, n, ...) are missing in the 
> output and
> only blank characters appear.
> Using an older version of the FreeType library, all characters are
> displayed
> correctly in both programs.
> 
> The font can be installed under Windows and all characters are OK, too.
> 
> During the conversion from Type1 to OTF, the "subroutinize" switch of
> Adobe's SDK was switched on.
> If the font is produced without setting the "subroutinize" flag, all
> characters
> are displayed correctly using FreeType 2.3.0, too.
> 
> Has this problem been reported already ? Any hint is appreciated.
> 
> Axel
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Freetype-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/freetype-devel