RE: [ft] Defective true type font

[Memory, Richard]

Hi,

Thanks; Is there a "porting guide" for the demos? I will be porting
ftview and ftgrid to a small graphics library that isn't supported. It
has a simple 2D raster type API that I will use to render the glyphs
(including bitmaps).

I can probably dig through the code and figure out, but if you have any
pointers of where to look first, that would be great. Which files to
compile if I'm using ftview, etc. 

Note that I have downloaded ft2demos-2.3.2.tar.gz since that is the
version of Freetype I am currently using.

Richard

> -----Original Message-----
> From: Werner LEMBERG [mailto:address@hidden 
> Sent: Tuesday, September 29, 2009 5:46 AM
> To: Memory, Richard
> Cc: address@hidden
> Subject: Re: [ft] Defective true type font
> 
> 
> > Is there an easy way to determine whether or not a true 
> type font is 
> > "defective" or not?
> 
> No.
> 
> > I have a custom font that seems to work on my Microsoft windows 
> > machine (more or less), but the glyphs produced by Freetype 
> are fuzzy 
> > and unreadable.
> 
> FreeType should be as compatible to the the MicroSoft 
> rasterizer as possible.  Please test the font extensively 
> with the FreeType demo programs (ftview, ftgrid, etc.) and 
> check whether the results are still bad if you switch between 
> the various rendering modes.  If you can confirm that the 
> problem persists I ask you to send me the font privately for 
> further investigation, together with an exact description how 
> to trigger the bad effects with one of the demo programs.
> 
> 
>     Werner
>