[Devel] RE: [Freetype] Bug with spaces in latest CVS release

[Manuel Bleichenbacher]

I've found the bug myself. It's a temporary hack in the file
truetype/ttgload.c starting at line 725:

Rather than:

    /* temporary hack */
#if 1
    if ( count < 10 )
    {
      /* This glyph is corrupted -- it does not have a complete header */
      error = TT_Err_Invalid_Outline;
      goto Fail;
    }
#endif

it sould be:


    /* temporary hack */
#if 1
    if ( count < 10 && count != 0 )
    {
      /* This glyph is corrupted -- it does not have a complete header */
      error = TT_Err_Invalid_Outline;
      goto Fail;
    }
#endif

It's rather obvious when you look at the code on the lines following the
"temporary hack":

    if ( count == 0 )
    {
      /* as described by Frederic Loyer, these are spaces, and */
      /* not the unknown glyph.                                */
      loader->bbox.xMin = 0;
      loader->bbox.xMax = 0;


-- Manuel


-----Original Message-----
From: address@hidden [mailto:address@hidden
Behalf Of Manuel Bleichenbacher
Sent: Montag, 17. Dezember 2001 1:39
To: address@hidden
Subject: [Freetype] Bug with spaces in latest CVS release


Hi,

I've upgraded an application from freetype 2.0.4 to the latest CVS release.
Now there's a problem with spaces.

All the different freetype functions I use (FTC_Image_Cache_Lookup,
FT_Load_Glyph, etc.) return an error if a try to load the space glyph. I
don't really need a bitmap for them but I need the advance width.

The demo application "ftstring" has the same problem, e.g. try:

  ftstring -m "The quick brown fox" 11 c:\windows\fonts\arial.ttf

Am I doing something wrong with space characters or has a bug been
introduced recently?

-- Manuel




_______________________________________________
Freetype mailing list
address@hidden
http://www.freetype.org/mailman/listinfo/freetype