nanogui: Fonts revisited
Re: Fonts revisited
"Vidar Hokstad" ####@####.####
19 Jan 2000 15:22:26 -0000
On Wed, 19 Jan 2000 07:56:37 -0500 Martin Jolicoeur ####@####.####
>I started looking at fonts too :-) (I'm full-time on this) But started to think
>about freetype rather than t1lib mostly because:
>- I wasn't correct in my previous E-mail saying that t1lib is smaller than
>freetype, actually t1lib is ~360k and freetype is ~270k (these values are for
>compiled with debugging symbols in, though)
My t1lib _without_ debuggin info is about 270kb.
>- Freetype was coded mainly for embedded systems, so the code is as fast as
>possible (it doesn't use floating point calculations, which is important for
>processors without fpu, like SA1100)
>- Freetype 2 (which is beta but seems quite stable) supports adobe t1 fonts
>new API that abstract the font type loaded (freetype 2 is bigger for this,
Do you know if Freetype 2 supports direct handling of kerning, and caching of
>I found a good number of truetype fonts on the net but didn't look at licenses
>... will do it now...
Good idea ;) If any of the truetype fonts you've found are redistributable
with commercial products _and_ "classic" (I'm looking for basic fonts like
times, helvetica, courier etc.), I'd love some pointers - I like truetype
technology a lot more than Type 1...
>Send me what you have as soon as it renders, I might change my opinion on the
>libs issue .... Still have some doc to read by then ...
I have something that renders now, but with some ugly hacks (hardcoded font
size, for one, and hardcoded color values ;).. I'll clean it up a bit, and make
a diff available ASAP (likely tomorrow).
I ended up doing antialiasing by default - it turned out to be easier to handle
than the non-antialiased call. Of course that makes it slower than it needs to
be, but it should be easy to fix the non-antialiasing code too.