Please update FREETYPE to 2.2!

aquila_deus · 2006-10-01 14:39:28

Here is a comparison between freetype 2.2 and older version:

Same font, freetype 2.2 with light hinting vs freetype 2 (default config on suse 10)

I heard people getting some problems with 2.2 - but the new light hinting is great (it doesn't make any difference before), and it works well with all the fonts I have tried: MS core fonts, new vista ones, and office fonts and chinese ones. Some fonts which can't be used with auto-hint previously are also rendered perfectly now.

Dusty · 2006-10-01 15:22:24

Its been flagged out of date, someone will get to it. It may help to file a bug report so the maintainers know that its important to someone. Update requests in this forum generally go unnoticed.

Dusty

Gullible Jones · 2006-10-01 15:29:05

Last time I used it, light hinting made my fonts look like little dark clouds.

At any rate, the problem with 2.2 is that bytecode hinting, rather than just being disabled by default, cannot be enabled, period. Unless someone's come up with a patch for that, in which case I'd by all means support the update.

aquila_deus · 2006-10-01 16:55:38

Gullible Jones wrote:

Last time I used it, light hinting made my fonts look like little dark clouds.
At any rate, the problem with 2.2 is that bytecode hinting, rather than just being disabled by default, cannot be enabled, period. Unless someone's come up with a patch for that, in which case I'd by all means support the update.

Ah, what fonts you are using?? Did you explicitly disable autohint for them in fonts.conf?

EDIT: I found the problem. Freetype 2.2 by default activates a stripped-down bytecode interpreter which has no patent issue (and is rather useless ), see http://freetype.fis.uniroma2.it/freetyp … ngine.html

I'm rebuilding a new freetype now

Gullible Jones · 2006-10-01 17:19:30

MS and Bitstream at the time, and yes, autohint was explicitly disabled.

FWIW, we had 2.2 in the repos for a while. It was reverted:

JGC wrote:

upgpkg: freetype2 2.1.10-4
Revert to 2.1.10, too many regressions. Add integer overflow fixes from Novell ClosedSuSE

aquila_deus · 2006-10-01 18:35:15

The freetype 2.2 with patented bytecode interpreter: http://www.aqd.ath.cx/stuff-linux/binar … pkg.tar.gz

patch is here => http://www.aqd.ath.cx/stuff-linux/bytecode.patch

JGC · 2006-10-01 18:59:16

Ah, seems that patch will solve the regressions: I found out after the first release that the bytecode hinter wasn't really enabled, so I updated it with a 2nd release, which became a little bit better, but was still worse than the 2.1.x versions.
Looking at your patch I need to disable/enable 3 options to get the old behaviour back.

Gullible Jones · 2006-10-01 22:08:27

Cool. 8)

Gustavo · 2006-10-09 03:19:34

Fonts are blurry here with the new freetype

EDIT: Sub-pixel hinting set to RGB and full hinting style fixed it.

GoneWacko · 2006-10-09 11:33:00

My xterms look hideous now

It's a bit of a shame that these kinds of gimicky changes get shoved down people's throats, in a way. Especially if it happens without warning or message in advance

Now I've been looking at how to switch this ugly anti-aliasing off for the last 30 minutes (and I've still not found the solution )

Gullible Jones · 2006-10-09 13:13:03

Are you using the autohinter or bytecode AA?

GoneWacko · 2006-10-09 13:34:22

To be honest, I haven't the slightest idea what I'm using

fonts.conf doesn't mention either of them, and the autohinter and AA parts are both commented out in /etc/fonts/local.conf.

in /etc/fonts/conf.d the only enabled config is no-bitmaps.conf

There is no ~/.fonts.conf, either.

aquila_deus · 2006-10-11 11:48:30

GoneWacko wrote:

To be honest, I haven't the slightest idea what I'm using
fonts.conf doesn't mention either of them, and the autohinter and AA parts are both commented out in /etc/fonts/local.conf.
in /etc/fonts/conf.d the only enabled config is no-bitmaps.conf
There is no ~/.fonts.conf, either.

On what apps??

GoneWacko · 2006-10-11 12:42:25

aquila_deus wrote:

GoneWacko wrote:
To be honest, I haven't the slightest idea what I'm using
fonts.conf doesn't mention either of them, and the autohinter and AA parts are both commented out in /etc/fonts/local.conf.
in /etc/fonts/conf.d the only enabled config is no-bitmaps.conf
There is no ~/.fonts.conf, either.
On what apps??

It looks fine everywhere, it's just that I don't want <the> to be applied to my xterm font because it doesn't look very well with that.

Arch Linux

#1 2006-10-01 14:39:28

Please update FREETYPE to 2.2!

#2 2006-10-01 15:22:24

Re: Please update FREETYPE to 2.2!

#3 2006-10-01 15:29:05

Re: Please update FREETYPE to 2.2!

#4 2006-10-01 16:55:38

Re: Please update FREETYPE to 2.2!

#5 2006-10-01 17:19:30

Re: Please update FREETYPE to 2.2!

#6 2006-10-01 18:35:15

Re: Please update FREETYPE to 2.2!

#7 2006-10-01 18:59:16

Re: Please update FREETYPE to 2.2!

#8 2006-10-01 22:08:27

Re: Please update FREETYPE to 2.2!

#9 2006-10-09 03:19:34

Re: Please update FREETYPE to 2.2!

#10 2006-10-09 11:33:00

Re: Please update FREETYPE to 2.2!

#11 2006-10-09 13:13:03

Re: Please update FREETYPE to 2.2!

#12 2006-10-09 13:34:22

Re: Please update FREETYPE to 2.2!

#13 2006-10-11 11:48:30

Re: Please update FREETYPE to 2.2!

#14 2006-10-11 12:42:25

Re: Please update FREETYPE to 2.2!

Board footer