Thanks to Dave, Vernon and Khaled for these replies. Khaled's solution
is the one that worked for me. I can't interpret the cryptic error
message ("0x06") that I got when I had two versions of Freetype
installed--perhaps ttfautohint was trying to use the wrong version.
But it's working now, and I look forward to playing around with it.Peter On Sun, Nov 6, 2011 at 4:52 PM, Dave Crossland <[email protected]> wrote: > :-) > > ---------- Forwarded message ---------- > From: Werner LEMBERG <[email protected]> > Date: 6 November 2011 01:04 > Subject: [ft-devel] ttfautohint 0.5 has been released > > ttfautohint 0.5 has been released. This time, rendering problems on iOS > should really be gone... > > It is available from > > http://savannah.nongnu.org/download/freetype/ > > or > > http://sourceforge.net/projects/freetype/files/ttfautohint > > Enjoy! > > > Werner > > > PS: Downloads from savannah.nongnu.org will redirect to your nearest > mirror site. Files on mirrors may be subject to a replication > delay of up to 24 hours. In case of problems use > http://download-mirror.savannah.gnu.org/releases/ > > > ---------------------------------------------------------------------- > > > This project provides a library which takes a TrueType font as the input, > remove its bytecode instructions (if any), and return a new font where all > glyphs are bytecode hinted using the information given by FreeType's > autohinting module. The idea is to provide the excellent quality of the > autohinter on platforms which don't use FreeType. > > The library has a single API function, `TTF_autohint'; see > `src/ttfautohint.h' for a detailed description. Note that the library > itself won't get installed currently. > > A simple command-line interface to the library is the demo program > `ttfautohint'; after compilation and installation, say > > ttfautohint --help > > for usage information, or say > > man ttfautohint > > to read its manual page. > > > ---------------------------------------------------------------------- > > > New in 0.5: > > * Rendering on iOS is now expected to give good results. > > * No bad rendering at very large PPEM values. > > _______________________________________________ > Freetype-devel mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/freetype-devel >
