You are not logged in.

#26 2007-03-20 00:28:57

eWoud
Member
Registered: 2005-07-06
Posts: 39

Re: new freetype2 suckx

The bad font spacing was the result of a typo, it was fixed in 2.3.2:

CHANGES BETWEEN 2.3.2 and 2.3.1

  I. IMPORTANT BUG FIXES

    - FreeType  returned incorrect  kerning information  from TrueType
      fonts when the bytecode  interpreter was enabled.  This happened
      due to a typo introduced in version 2.3.0.

(Archlinux has the bytecode interpreter enabled by default)


tea is overrated

Offline

#27 2007-03-27 15:08:40

Weeks
Member
Registered: 2006-01-26
Posts: 91

Re: new freetype2 suckx

Even with the bytecode interpreter enabled - as it seems to be by default - my fonts were crappy, I'd say smudged more than anything. Anyway I appear to have fixed the problem - well more updated the wiki to give an explanations on why some else's tip actually works wink. All hail the patent-free autohinter. I wouldn't say the fonts are as good as xp or osx's, but they're much better than what they were per default and satisfactory.

[edit] Actually, I'm really impressed with the autohinter.

Last edited by Weeks (2007-03-27 18:57:28)

Offline

Board footer

Powered by FluxBB