> > It would probably be rather slow, but it's nice as an option.
>
> Actually, I really wanted to use t1lib for our font rendering, since
> we would get anti-aliasing support that way. However, your prediction
> of it being "rather slow" understates things pretty dramatically.
Good. I was practicing the ways of communication with cultures where
such statement would be a normal and polite way of indicating that
although it's a nice feture, some users might want to have a way
for turning it off. If you intend to go into I18N things, I'm
afraid you'll have to learn to deal with these things. :-)
> We actually implemented it, by integrating t1lib into the app and
> trying it out. Even with anti-aliasing turned off, it was very
> slow. Really, really slow. The continental drift is noticeably
> faster.
I never programmed anything with t1lib, so I can't tell. Although I
think I remember that the code was not brilliant, but I compiled it a
long time ago, so I might be wrong. Anyway, how slow compared to
Adobe's Acrobat reader? It does anti-aliasing too, but with Adobe's
proprietary code. I find Acrobat too slow, but some people don't.
--
.-. .-. Life is a sexually transmitted disease.
(_ \ / _)
| dave@srce.hr
| dave@fly.cc.fer.hr