[Bug 243558] New: Arial font major rendering regression on SUSE 10.2 (from 10.1)
https://bugzilla.novell.com/show_bug.cgi?id=243558 Summary: Arial font major rendering regression on SUSE 10.2 (from 10.1) Product: openSUSE 10.2 Version: Final Platform: i686 OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: X11 Applications AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: ashaduri@yandex.ru QAContact: sndirsch@novell.com I have two installations of SUSE - 10.1 and 10.2. I've been able to achieve extremely high quality rendering for Arial font using the ~/.fonts.conf file below (AA enabled, full hinting, autohint enabled) on SUSE 10.1 (that is, freetype2-2.1.10-16). However, in SUSE 10.2 (with bundled freetype2-2.2.1.20061027-11) its impossible to achieve something even close to that. I've fiddled with many settings (hinting style, autohint), but the rendering quality is just unacceptable for Arial (I'll attach the screenshots). I also tried freetype2-2.3.0-5.1 (from http://software.opensuse.org/download/GNOME:/UNSTABLE/openSUSE_10.2/src/free...) - it was a little better than 2.2.1, but still bad (I didn't take any screenshots of it). Then, I downloaded freetype2 2.3.1 tarballs from the freetype site, and adapted the rpm spec file from freetype2-2.3.0-5.1 (I left all the patches as they were). The result is that the rendering is much better than 2.2.1 and 2.3.0, but still worse than 2.1.10. Of course, I understand that "better" and "worse" are somewhat subjective, but all the versions after 2.1.10 have the rendering artifacts which may be considered as bugs, so it's not only pretty vs less pretty, but there are actual issues there. The composite screenshots of 3 versions (2.1.10, 2.2.1, 2.3.1) (10pt and 9pt sizes) will be attached. 2.2.1 is clearly worse than 2.1.10; 2.3.1 looks almost the same as 2.1.10 at 10pt, but on closer inspection it has some spacing issues - note the third line with "1234...". It's especially apparent at 9pt. Also, the number '9' looks real ugly on 2.3.1 (9pt). The text editor on the screenshots is kwrite. So, to sum up, the freetype versions are: freetype2-2.1.10-16 (bundled with SUSE 10.1 I think) on SUSE 10.1 - very good. freetype2-2.2.1.20061027-11 - (bundled with SUSE 10.2) on SUSE 10.2- horrible. freetype2-2.3.0-5.1 (from GNOME unstable repository on opensuse.org) on SUSE 10.2 - little better than 2.2.1. freetype2-2.3.1-5.1 (my package) on SUSE 10.2 - much better, but still worse than 2.1.10. Has some rendering glitches. I tried to install 2.1.10 on SUSE 10.2, but there's some dynamic linker error at runtime in some Xft library, so I gave up. As I understand it, all these versions have the bytecode interpreter enabled during compile time. I would post this to freetype bugzilla, but there seems to be no such thing. Also, I know that SUSE has somewhat patched versions of freetype2, so I doubt they would give support for that. I'm using a CRT display (Samsung 753DFX), so no subpixel hinting is enabled. Contents of the ~/.fonts.conf file (both distributions): <?xml version="1.0"?> <!DOCTYPE fontconfig SYSTEM "fonts.dtd"> <fontconfig> <match target="font" > <edit mode="assign" name="rgba" > <const>none</const> </edit> </match> <match target="font" > <edit mode="assign" name="hinting" > <bool>true</bool> </edit> </match> <match target="font" > <edit mode="assign" name="hintstyle" > <const>hintfull</const> </edit> </match> <match target="font" > <edit mode="assign" name="autohint" > <bool>true</bool> </edit> </match> <match target="font" > <edit mode="assign" name="antialias" > <bool>true</bool> </edit> </match> <match target="font" > <edit mode="assign" name="dpi" > <double>96</double> </edit> </match> </fontconfig> -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=243558 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |mfabian@novell.com |screening@forge.provo.novell| |.com | -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=243558 ------- Comment #1 from ashaduri@yandex.ru 2007-02-08 07:49 MST ------- Created an attachment (id=118081) --> (https://bugzilla.novell.com/attachment.cgi?id=118081&action=view) Comparison - full hinting, autohint, 10pt Note the spacing issue on 2.3.1 - especially the third line with "123...". -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=243558 ------- Comment #2 from ashaduri@yandex.ru 2007-02-08 07:49 MST ------- Created an attachment (id=118082) --> (https://bugzilla.novell.com/attachment.cgi?id=118082&action=view) Comparison - full hinting, autohint, 9pt Note the spacing issue on 2.3.1. Also, the number '9' looks really ugly. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=243558 ------- Comment #3 from ashaduri@yandex.ru 2007-02-08 07:56 MST ------- I forgot to mention that both X font resolution (xdpyinfo | grep resolution) and Xft resolution (xrdb -query | grep Xft) return 96dpi. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=243558 ------- Comment #4 from ashaduri@yandex.ru 2007-02-08 08:05 MST ------- Created an attachment (id=118087) --> (https://bugzilla.novell.com/attachment.cgi?id=118087&action=view) All taken screenshots - 2.1.10, 2.2.1 and 2.3.1 compared. All screenshots - 2.1.10, 2.2.1 and 2.3.1 compared with full/medium hinting, autohint on/off, 10pt/9pt sizes. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=243558 mfabian@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=243558 ------- Comment #5 from mfabian@novell.com 2007-02-09 12:45 MST ------- alex shaduri> I would post this to freetype bugzilla, but there seems to be no such thing. You can post that to the freetype mailing list. alex shaduri> Also, I know that SUSE has somewhat patched versions of freetype2, so I doubt alex shaduri> they would give support for that. Only very minimal. Currently (openSUSE 10.2), the only patches which has any effect on rendering is compiling in the byte code interpreter which is not compiled in by default upstream. And if you use autohint=true as you write, the byte code interpreter isn't used anyway, i.e. there are no patches at all in the SuSE freetype2 package which make any difference for you compared to the upstream freetype. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=243558 ------- Comment #6 from mfabian@novell.com 2007-02-09 12:56 MST ------- alex shaduri> freetype2-2.3.1-5.1 (my package) on SUSE 10.2 By the way, you can the freetype2-2.3.1 package from the current development version of openSUSE 10.3 build for openSUSE 10.2 from here: http://software.opensuse.org/download/M17N/openSUSE_10.2/ http://software.opensuse.org/download/M17N/openSUSE_10.2/i586/freetype2-2.3.... http://software.opensuse.org/download/M17N/openSUSE_10.2/i586/freetype2-deve... That should make no difference to the rendering you see with the freetype you build yourself though. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=243558 ------- Comment #7 from mfabian@novell.com 2007-02-09 13:07 MST ------- Mike> Only very minimal. Currently (openSUSE 10.2), the only patches which Mike> has any effect on rendering is compiling in the byte code interpreter Mike> which is not compiled in by default upstream. The same was the case for the freetype 2.1.10 package in SUSE Linux 10.1. This package had a patch applied to improve the rendering with the autohinter compared to the freetype 2.1.10 release, but this patch came from the upstream CVS as you can see in the freetype2.spec file from SUSE Linux 10.1: # CJK autofit from upstream CVS Patch5: bugzilla-157441-autofit-cjk-cvs.patch I.e. the changes you see in the rendering of the autohinter have nothing to do with SuSE patches, it has changed upstream like this. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=243558 ------- Comment #8 from mfabian@novell.com 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.
https://bugzilla.novell.com/show_bug.cgi?id=243558 mfabian@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WORKSFORME ------- Comment #9 from mfabian@novell.com 2007-02-09 13:29 MST ------- You may report the rendering glitch with the ‘9’ upstream if you like. It is probably better to use ftview to reproduce it instead of using a KDE/Gnome/whatever program to show that it is purely a freetype problem and not caused by Pango/Xft/whatever. You can reproduce it easily with: ftview -r 96 9 /usr/share/fonts/vista/arial.ttf (and then hit ‘f’to force the autohinter) I'm closing this bug as WORKSFORME because the default on openSUSE for Arial (autohint=false) renders just fine. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=243558
------- Comment #10 from mfabian@novell.com 2007-02-09 13:31 MST -------
I added Werner LEMBERG
https://bugzilla.novell.com/show_bug.cgi?id=243558 ------- Comment #11 from ashaduri@yandex.ru 2007-02-09 14:06 MST ------- Thanks, I'll try to bug the freetype developers through their mailing list. As for the size 9 screenshots, I attached them just to show that the glyph '9' was really broken. I myself use the Arial size 10 as my system font, and it's less blurry. That is, not blurry enough to irriate me, while keeping the wonderful shapes. The blurriness may actually depend on the monitor (I think), so you may be seeing a different picture on your monitor than I'm seeing on mine. I'm looking at size10 screenshots for 2.1.10/hintfull/autohint and the same with noautohint right now. The main problems for me with autohint=false are: 1. Some glyphs have problems with proportions - see B, S, 8 (the fourth line). 2. Some glyphs are too square-like - Q, G, Q, D. 3. The line widths in glyphs change strangely - O, 2. 4. Some glyphs are a little bolder than the others - a, s, w. 5. Some shapes are really damaged - s, a (look at a's "hole"). I kind of wonder how the same font can look so different - I mean, the glyphs look like it's totally other font (especially the comma ','). A quick look with ftview shows the same results. I'll try to recapture the images anyway... OK, off to freetype mailing list then (if my points above don't suffice to re-open this entry). -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=243558 wl@gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |david@freetype.org ------- Comment #12 from wl@gnu.org 2007-02-10 07:56 MST ------- I can confirm the problem with glyph `9' of arial.ttf, version 3.00, using the autohinter at 12ppem. It seems that some fine-tuning has improved many other shapes but degraded this particular one. David is going to further improve the autohinter, he has told me. Just as a remainder for us I ask you to file a bug report at https://savannah.nongnu.org/bugs/?group=freetype -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=243558 ------- Comment #13 from mfabian@novell.com 2007-02-10 13:58 MST ------- Werner LEMBERG> Just as a remainder for us I ask you to file a bug report at Werner LEMBERG> Werner LEMBERG> https://savannah.nongnu.org/bugs/?group=freetype I just did that. Thank you very much! -- 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.
participants (1)
-
bugzilla_noreply＠novell.com