On Sun, Jan 02, 2011 at 08:07:03AM +0100, Werner LEMBERG wrote:
The trickyness is that you are trying to separate hinting
from rasterizing. As explained already, the TrueType
bytecode interpreter and the rasterizer do interact. It's
not intended to be handled separately.
I went
...just to extract outlines.
And by the way, the autohinting module works pretty damn good!
--- On Sat, 1/1/11, Werner LEMBERG w...@gnu.org wrote:
From: Werner LEMBERG w...@gnu.org
Subject: Re: [ft] Bytecode hinter producing bad results, seems to be a
regression
To: thev...@yahoo.com
Cc
check your font whether my assumption is correct. I only have
`Helvetica Neue LT Pro 65 Medium' version 001.000 (from 2003), but
this is an OpenType font with CFF outlines.
Accidentally, I've also found `Helvetica Neue LT Com 65 Medium' (2.01
from 2006). My assumption was correct: The
The function FT_Get_Gasp tells you,
for a given ppem, whether you should
render a glyph as monochrome
(i.e., black-white) or with anti-aliasing.
ppem? is that what I understand to be the font height? Pixels per EM unit? By
monochrome I assume you mean, two intensity levels (on or off). As
You haven't told us which FreeType version you are
using... For bug
reports, please always try the recent one, this is, 2.4.4.
Sorry about that and yes of course I'm using the most recent version.
BTW, I'm not sure that `professional' fonts are intended
for screen display, working at small
From: Vinnie thev...@yahoo.com
Subject: Re: [ft] Bytecode hinter producing bad results, seems to be a
regression
Date: Sat, 1 Jan 2011 12:20:06 -0800 (PST)
The function FT_Get_Gasp tells you, for a given ppem, whether you
should render a glyph as monochrome (i.e., black-white) or with
anti
The trickyness is that you are trying to separate hinting
from rasterizing. As explained already, the TrueType
bytecode interpreter and the rasterizer do interact. It's
not intended to be handled separately.
I went through the trouble of tweaking my 3rd party library to support
rendering
So it seems that the font I have is unhinted, hence the small size.
No. It's hinted.
I just assumed that all TrueType/OpenType fonts that came from
Linotype or other well recognized foundries were loaded to the gills
with hints but it seems I am mistaken.
Helvetica originally is a Type 1
The trickyness is that you are trying to separate hinting
from rasterizing. As explained already, the TrueType
bytecode interpreter and the rasterizer do interact. It's
not intended to be handled separately.
I went through the trouble of tweaking my 3rd party library to
support rendering
Several months ago I noticed that the output of Freetype was worse for my
application. I've returned to working on that part of my application and now I
have something concrete. It seems the bytecode hinter is defective, and the
autohinter is working. Check out this image:
10 matches
Mail list logo
