suse 8.2 and freetype2 autohinter
![](https://seccdn.libravatar.org/avatar/538dfd57402d8edcee2ef1cef7e768c7.jpg?s=120&d=mm&r=g)
Hi, Just install 8.2 (ftp), and found out that XFree86 (or KDE?) renders non-antialiased fonts without autohinting capability, even if the freetype2 is compiled with autohinting enabled. Any ideas? -- -- Verdi March --
![](https://seccdn.libravatar.org/avatar/538dfd57402d8edcee2ef1cef7e768c7.jpg?s=120&d=mm&r=g)
On Tuesday 13 May 2003 19:04, Verdi March wrote:
Hi,
Just install 8.2 (ftp), and found out that XFree86 (or KDE?) renders non-antialiased fonts without autohinting capability, even if the freetype2 is compiled with autohinting enabled.
Any ideas?
Sorry, replace "autohinting" with "bytecode interpreter" -- -- Verdi March --
![](https://seccdn.libravatar.org/avatar/0724cd2fec38c7b6f662bb7fda14c68c.jpg?s=120&d=mm&r=g)
On Tue, 13 May 2003 19:19:41 +0800
Verdi March
Sorry, replace "autohinting" with "bytecode interpreter"
It sounds like you didn't upgrade freetype2. From Freetype 2.4.x on wards you shouldn't need to enable the "bytecode interpreter". This is due to the fact that the auto-hinting is now as good as and, in some cases, surpass that of the "bytecode interpreter". Charles -- Running Windows on a Pentium is like having a brand new Porsche but only be able to drive backwards with the handbrake on. (Unknown source)
![](https://seccdn.libravatar.org/avatar/538dfd57402d8edcee2ef1cef7e768c7.jpg?s=120&d=mm&r=g)
On Tuesday 13 May 2003 19:53, Charles Philip Chan wrote:
It sounds like you didn't upgrade freetype2. From Freetype 2.4.x on wards you shouldn't need to enable the "bytecode interpreter". This
Hm, but suse 8.2 includes freetype 2.1.3. Anyway, I'll try compiling 2.1.4 now. -- -- Verdi March --
![](https://seccdn.libravatar.org/avatar/0724cd2fec38c7b6f662bb7fda14c68c.jpg?s=120&d=mm&r=g)
On Tue, 13 May 2003 20:00:05 +0800
Verdi March
Hm, but suse 8.2 includes freetype 2.1.3. Anyway, I'll try compiling 2.1.4 now.
Use the version in this directory instead: ftp://ftp.suse.com/pub/people/mfabian/8.2-src There are bug fixes that are not in the official tarball. While you are at it, you might want to consider upgrade fontconfig to 2.2 also. Charles -- I've run DOOM more in the last few days than I have the last few months. I just love debugging ;-) (Linus Torvalds)
![](https://seccdn.libravatar.org/avatar/538dfd57402d8edcee2ef1cef7e768c7.jpg?s=120&d=mm&r=g)
On Tuesday 13 May 2003 19:53, Charles Philip Chan wrote:
It sounds like you didn't upgrade freetype2. From Freetype 2.4.x on wards you shouldn't need to enable the "bytecode interpreter". This is due to the fact that the auto-hinting is now as good as and, in some cases, surpass that of the "bytecode interpreter".
I think I need to clarify. When I use freetype with bytecode interpreter in Suse 7.2, 8.0, or 8.1, I can notice the difference of non-antialised fonts quality. However, in 8.2, even when I use bytecode interpreter, fonts are displayed as if freetype2 does not have bytecode interpreter enabled. -- -- Verdi March --
![](https://seccdn.libravatar.org/avatar/0724cd2fec38c7b6f662bb7fda14c68c.jpg?s=120&d=mm&r=g)
On Tue, 13 May 2003 20:06:11 +0800
Verdi March
However, in 8.2, even when I use bytecode interpreter, fonts are displayed as if freetype2 does not have bytecode interpreter enabled.
Sorry, I can't help you here since I am still on 8.1. Maybe our local fonts and Linux print system guru, Mike Fabian can answer this one :-). Have anyone else using 8.2 experienced the same problem? Charles -- "sic transit discus mundi" (From the System Administrator's Guide, by Lars Wirzenius)
![](https://seccdn.libravatar.org/avatar/538dfd57402d8edcee2ef1cef7e768c7.jpg?s=120&d=mm&r=g)
On Tuesday 13 May 2003 20:19, Charles Philip Chan wrote:
On Tue, 13 May 2003 20:06:11 +0800
Verdi March
wrote: However, in 8.2, even when I use bytecode interpreter, fonts are displayed as if freetype2 does not have bytecode interpreter enabled.
Sorry, I can't help you here since I am still on 8.1. Maybe our local fonts and Linux print system guru, Mike Fabian can answer this one :-).
Have anyone else using 8.2 experienced the same problem?
Ok, just finish recompiling 2.1.4, and now it seems to work again, non-antialiased fonts are displayed with bytecode interpreter enabled. -- -- Verdi March --
![](https://seccdn.libravatar.org/avatar/0724cd2fec38c7b6f662bb7fda14c68c.jpg?s=120&d=mm&r=g)
On Tue, 13 May 2003 20:54:45 +0800
Verdi March
Ok, just finish recompiling 2.1.4, and now it seems to work again, non-antialiased fonts are displayed with bytecode interpreter enabled.
Great. If you have some time, you might want to try it with the "bytecode interpreter" turned off (thus using the auto-hinting module instead) to see which one you prefer. Charles -- "Nature abhors a Vacuum" -- Brian Behlendorf on OSS (Open Sources, 1999 O'Reilly and Associates)
![](https://seccdn.libravatar.org/avatar/538dfd57402d8edcee2ef1cef7e768c7.jpg?s=120&d=mm&r=g)
On Tuesday 13 May 2003 21:06, Charles Philip Chan wrote:
Great. If you have some time, you might want to try it with the "bytecode interpreter" turned off (thus using the auto-hinting module instead) to see which one you prefer.
I notice there's improvement in 2.1.4, but still, with bytecode interpreter, true type fonts are rendered smoother. But it doesn't matter anyway, since now I always turn on antialias. Just realized how good antialias is. -- -- Verdi March --
participants (2)
-
Charles Philip Chan
-
Verdi March