Mailinglist Archive: opensuse-bugs (8107 mails)

< Previous Next >
[Bug 243558] Arial font major rendering regression on SUSE 10.2 (from 10.1)
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Fri, 9 Feb 2007 13:23:29 -0700 (MST)
  • Message-id: <20070209202329.BFE34D40@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=243558





------- Comment #8 from mfabian@xxxxxxxxxx 2007-02-09 13:23 MST -------
Some comments to the screen shots you attached to comment #4:

ft2110_hintfull_autohint_size9.png:

quite blurry. It doesn't have the rendering glitch with the ‘9’
as seen in the next screen shot, but it is far too blurry for my
taste.

ft231_hintfull_autohint_size9.png:

Has an obvious rendering glitch in the glyph for ‘9’, that's right.
And the spacing is indeed a bit more uneven than in the previous screen
shot.
I don't mind the “123” that much, but the spacing in the word
“FreeType”
looks a bit weird to me.
A little less blurry than the previous screen shot but still too blurry
for my test.

ft2110_hintfull_noautohint_size9.png
ft231_hintfull_noautohint_size9.png

These two screen shot are using the byte code interpreter. They are
identical
because the rendering with the byte code interpreter didn't change.

I think they are *far* better than the screen shots created with the
autohinter.
*Very* sharp, no rendering glitches at all.

Why don't you use these?

As these are clearly the best, autohint=false is the default for Arial on
openSUSE 10.2.


--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

< Previous Next >
References