Re: [Fontforge-devel] bytecode debugging issues

[Werner L. <wl...@gn...>]

[Executable based on sources from 17:12 15-Nov-2005-ML.]

> > Please add an option to the `raster' window used during debugging
> > to display the glyph as grayscale.  Fonts like `Vera' are hinted
> > for grayscale only, according to its `gasp' table.
>
> Given my implementation, it was easier just to make everything
> either grey or mono.  So you get to choose when you start the
> debugger, setting the display in the raster window and the debug
> window itself.

Very, very nice!

> If a pixel changes it will be shown in green rather than grey (if a
> pixel is 0xRRGGBB, and it changes then ff will show 0x00GG00)

What do you think of reducing the number of gray values used in the
main debugging window, avoiding too dark colours so that the contours
can be seen better?  Additionally I suggest to make the background of
the small `raster' window really white.

> > Another problem: As mentioned on the FreeType list, the `K' glyph
> > from Vera.ttf displayed at 10pt (with 72dpi) looks strange.
> > Debugging it with FontForge (using the CVS version of FreeType)
> > gives a completely different result to what FreeType yields (with
> > anti-aliasing disabled).  Is this an artefact how the apparently
> > self-intersecting contour is rasterized?

Just for completeness: It was a bug in FreeType.

> I don't know how to use freetype to get a mono bitmap from an
> FT_Outline, [...]

Hmm, maybe you should bring this topic on freetype-devel; perhaps
David has ideas.

> Changes are too big to provide a patch and are in the cvs tree.

Thanks a lot!


    Werner


PS: The problem with sfddiff (not automatically compiled but required
    for `make install') is still there.