Richard Neill wrote: > >> Shouldn't antialiasing be enabled? > >> > > If it is fonts looks blured. I have BTC enabled on my Slackware box > and it looks good without antialiasing. > >> Also, could you provide a more detailed info on what fonts do you have > >> installed? (I do not know what you mean with "all MS ttf fonts"). > >> > > > I reported this bug 6 months ago at the time of 2007.0 Beta. I'm > horrified to hear it still hasn't been fixed! I think that the PLF > libfreetype6 has been compiled without the bytecode interpreter being > properly enabled.
Yes, there was a bug that prevented the bytecode interpreter being enabled, but I fixed that in 2.2.1-8plf. > Everything was fine in 2006, (and in fact for years before that). Could > the person who compiled libfreetyp6 for the plf perhaps do a diff > against the previous version to see what changed? The most major change is the freetype upgrade 2.1 => 2.2, which changed the way bytecode interpreter was enabled. Therefore it was broken before 2.2.1-8plf. > > If any more info is needed on how it *should* work, please see my > webpage here, referring to Mdv 2006. It includes some images. > http://www.richardneill.org/a22p-mdk11-0.php#fonts I tried with Arial, antialiasing disabled. With 2.2.1-4mdv, I see it like http://www.richardneill.org/images/font-antialiasing-hinting-samples/spidery.png But with 2.2.1-8plf, the Arial font renders properly (i.e. hinted). Could someone please provide the name of some font that has the problem, so that I could reproduce and fix it sometime? > > Alternatively (much as I hate to say this), use a Debian based distro > (Debian/Knoppix/Ubuntu), because they just ignore the software patent, > and build libfreetype correctly in the main distro. > [That said, Ubuntu Edgy has a bug in OpenOffice fonts, which is specific > to OOo, but rather nasty] -- Anssi Hannula _______________________________________________ PLF-discuss mailing list [email protected] https://www.zarb.org/mailman/listinfo/plf-discuss
