Werner LEMBERG w...@gnu.org writes:
Today in the morning, while still dozing, I had a great idea how to
largely simplify hinting of composite glyphs, and which solves the
Roboto issue at the same time.
Heh, you have your best coding ideas while half-asleep too eh...?
:}
-miles
--
Monday,
Today in the morning, while still dozing, I had a great idea how to
largely simplify hinting of composite glyphs, and which solves the
Roboto issue at the same time. In particular, I believe that I've
found a way to completely avoid fiddling with point indices.
Following this route I shot
While testing google's new Roboto font (version 1.0), I found out
that ttfautohint 0.6 crashes, unfortunately. Reason is the very
weird glyph `nonbreakingspace' (its bbox is xMin=32767, yMin=32767,
xMax=-32767, yMax=-32767, BTW) which is a composite glyph with a
single component, namely
Could this be the same reason why 0.6 crashes for me on osx with a
segmentation fault when autohinting any font?
Of course not :-) What font have you tried?
Werner
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
GMT+00:00
Subject: Re: [ft-devel] ttfautohint 0.6 has been released
ttfautohint 0.6 has been released.
While testing google's new Roboto font (version 1.0), I found out that
ttfautohint 0.6 crashes, unfortunately. Reason is the very weird
glyph `nonbreakingspace' (its bbox is xMin=32767, yMin
ttfautohint 0.6 has been released.
While testing google's new Roboto font (version 1.0), I found out that
ttfautohint 0.6 crashes, unfortunately. Reason is the very weird
glyph `nonbreakingspace' (its bbox is xMin=32767, yMin=32767,
xMax=-32767, yMax=-32767, BTW) which is a composite glyph
ttfautohint 0.6 has been released.
It is available from
http://savannah.nongnu.org/download/freetype/
or
http://sourceforge.net/projects/freetype/files/ttfautohint
Merry Xmas!
Werner
PS: Downloads from savannah.nongnu.org will redirect to your nearest
mirror site. Files
