Robert: El Jue 23 Jun 2005 04:11, Robert Graf-Waczenski escribió:
The freetype web page also mentions that their pixel-hinting algorithms are actually better than the bytecode interpreter, so they recommend to not enable it but to instead use their pixel-hinting algorithms.
In my experience it's the bytecode interpreter which gives the best result, and not the pixel-hinting algorithms which by all means seem to be just the second-best alternative in case the patent issues have you worried.
./configure make make install
For freetype2, i also had to copy the resulting library files from /usr/local/lib to /usr/lib, but this was also done in a few seconds.
This you could have avoided by doing './configure --prefix=/usr'.
I then restarted my KDE session and.... Wow! I must have been blind previously!
Exactly my experience. Now the font rendering is as nice as - or better - as in WIndows, isn't it?
Did anybody encounter similar difficulties?
What difficulties?
Can anybody describe a method to get a similarly crisp and clean font display *without* the patented bytecode interpreter?
As I mentioned before, for crisp fonts on Linux desktops nothing comes even close to using the freetype2 library with the bytecode interpreter enabled. That three patents held by Apple are the cause for this library not being distributed by default with the active bytecode interpreter is a real shame! -- Andreas Philipp Noema Ltda. Bogotá, D.C. - Colombia http://www.noemasol.com