Fonts gone to hell after latest dist-upgrade from Dag

Place to discuss Fedora and/or Red Hat
Post Reply
User avatar
Void Main
Site Admin
Site Admin
Posts: 5712
Joined: Wed Jan 08, 2003 5:24 am
Location: Tuxville, USA
Contact:

Fonts gone to hell after latest dist-upgrade from Dag

Post by Void Main » Wed Jun 01, 2005 7:52 pm

I noticed after I upgraded my machine today the fonts looked very crappy in all of my apps. I noticed freetype was upgraded so I checked out the latest entry in the Changelog (rpm -q freetype --changelog | head).

Code: Select all

* Tue May 31 2005 Avi Alkalay <avibrazil@gmail.com> - 2.1.9-1
- Enabled bytecode interpreter for better screen font rendering.
Well I beg to differ. If you want your fonts back the way they were just install the latest SRPM:

Code: Select all

rpm -i http://dag.wieers.com/packages/freetype/freetype-2.1.9-1.rf.src.rpm
Replace your RPMROOT/SPECS/freetype.spec with mine:
http://voidmain.is-a-geek.net/files/specs/freetype.spec

Then build it with "rpmbuild -ba freetype.spec". Upgrade your freetype:

Code: Select all

# rpm -Fvh RPMROOT/RPMS/i386/freetype*rpm
Now you have a new changelog:

Code: Select all

* Wed Jun 01 2005 Void Main <voidmain AT linuxmail.com> - 2.1.9-2
- Disabled bytecode interpreter for better screen font rendering.

* Tue May 31 2005 Avi Alkalay <avibrazil@gmail.com> - 2.1.9-1
- Enabled bytecode interpreter for better screen font rendering.
:)

After you restart X you should have your fonts back to the way they were. Of course you could just install the old one but this is more fun.

Tux
guru
guru
Posts: 689
Joined: Wed Jan 08, 2003 10:40 am

Post by Tux » Thu Jun 02, 2005 4:18 pm

Thanks void, saved me some tme there.

User avatar
Void Main
Site Admin
Site Admin
Posts: 5712
Joined: Wed Jan 08, 2003 5:24 am
Location: Tuxville, USA
Contact:

Post by Void Main » Thu Jun 02, 2005 8:11 pm

Dag's note on the subject:

http://lists.freshrpms.net/pipermail/fr ... 13135.html
The freetype library now includes the bytecode interpreter, which is a big
win for truetype fonts that include proper hinting, but worse for those
fonts that rely on anti-aliasing. (sadly few fonts provide proper hinting)

We're looking into getting the best of both worlds (ie. enable
anti-aliasing for those fonts that do not have proper hinting)

In the worst case I will revert the change (ie. release the original
freetype without the bytecode interpreter). But the results look better on
my desktop and I didn't make a change, but I'm using the right fonts with
hinting support apparently.

See this message as an admission that I shouldn't have added it like that.
But with the support of the author of the Font HOWTO and my own
(improved) experience I made that call. And I now regret that.

I'd like to provide the fonts that have proper hinting (currently you have
to download them from the link in the Font HOWTO).

Sorry for those that have been affected, you know how to revert the
change manually or wait until I've figured out to get the best of both
worlds.

worker201
guru
guru
Posts: 668
Joined: Sun Jun 13, 2004 6:38 pm
Location: Hawaii

Post by worker201 » Fri Jun 03, 2005 6:07 am

What a great guy! Lots of people wouldn't have even bothered with an explanation.

Tux
guru
guru
Posts: 689
Joined: Wed Jan 08, 2003 10:40 am

Post by Tux » Fri Jun 03, 2005 6:31 am

Wasn't the bytecode interpreter originally omitted from binaries for some legal reason.
What has changed?

Post Reply