[Bug 227498] New: full and none hinting selections are reversed in GTK apps
https://bugzilla.novell.com/show_bug.cgi?id=227498 Summary: full and none hinting selections are reversed in GTK apps Product: openSUSE 10.2 Version: Final Platform: i386 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: kde-maintainers@suse.de ReportedBy: mrmazda@ij.net QAContact: qa@suse.de To reproduce: 1-on new KDE 10.2 installation, open some GTK app (e.g. - Wireshark and/or SeaMonkey) 2-note spindly looking menu fonts 3-open KControl to Appearance & Themes -> Fonts -> Use anti-aliasing for fonts 4-note anti-aliasing is enabled 5-note Hinting style is set to full 6-close the GTK apps 7-change the hinting style to none, and apply 8-reopen GTK apps Actual behavior: 1-with hinting set to full hinting is off 2-with hinting set to none hinting is maximum Expected behavior: 1-with hinting set to full hinting is maximum 2-with hinting set to none hinting is off -- 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=227498 ------- Comment #1 from mrmazda@ij.net 2006-12-10 17:35 MST ------- Created an attachment (id=109059) --> (https://bugzilla.novell.com/attachment.cgi?id=109059&action=view) left to right 1600x1200 120 DPI screenshot of none, slight, medium, & full (4065x478) this is actually 4 screenshots merged for easy comparison -- 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=227498 ------- Comment #2 from mrmazda@ij.net 2006-12-10 17:35 MST ------- Created an attachment (id=109060) --> (https://bugzilla.novell.com/attachment.cgi?id=109060&action=view) top to bottom 1600x1200 120 DPI screenshot of none, slight, medium, & full (1015x1878) this is actually 4 screenshots merged for easy comparison -- 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=227498 mrmazda@ij.net changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |http://mrmazda.no-ip.com/auth/dpi-screen- | |window.html ------- Comment #3 from mrmazda@ij.net 2006-12-10 17:40 MST ------- URL is page displayed in SeaMonkey in the screenshots. SeaMonkey for those screenshots has been set to DejaVu Sans Condensed (same as the KDE desktop setting) as preference default. http://mrmazda.no-ip.com/auth/dpi-screen-window.html -- 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=227498 coolo@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |mrmazda@ij.net ------- Comment #4 from coolo@novell.com 2006-12-11 04:58 MST ------- please look at `xrdb -query | grep Xft` and in your ~/.fonts.conf - do the values in there look correct? -- 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=227498 ------- Comment #5 from mrmazda@ij.net 2006-12-11 14:06 MST ------- I believe this is correct for the current full setting: # xrdb -query | grep Xft Xft.antialias: 1 Xft.hinting: 1 Xft.hintstyle: hintfull Xft.rgba: none # cat .fonts.conf <?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="antialias" > <bool>true</bool> </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=227498 coolo@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kde-maintainers@suse.de |bnc-team-gnome@forge.provo.novell.com Status|NEEDINFO |NEW Component|KDE |GNOME Info Provider|mrmazda@ij.net | ------- Comment #6 from coolo@novell.com 2006-12-12 02:43 MST ------- then this should be a bug in gtk -- 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=227498 sven.burmeister@gmx.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sven.burmeister@gmx.net ------- Comment #7 from sven.burmeister@gmx.net 2006-12-21 05:26 MST ------- Might this also be an explanation for XFCE not using the settings provided by fontconfig? I have Opera (Qt) installed and it seems to render the ttf-fonts with bytecode whereas the rest of XFCE looks as if they would not use it. -- 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=227498 ------- Comment #8 from mhejpetr@mhn.cz 2006-12-24 01:25 MST ------- Probably same problem here. Hinting style: medium, fonts look in GTK applications different. See attached picture. -- 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=227498 ------- Comment #9 from mhejpetr@mhn.cz 2006-12-24 01:27 MST ------- Created an attachment (id=111012) --> (https://bugzilla.novell.com/attachment.cgi?id=111012&action=view) Hinting style: medium. Fonts look in QT and GTK apps. different. -- 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=227498 ------- Comment #10 from maacruz@gmail.com 2007-01-13 12:56 MST ------- The problem is located in /etc/fonts Investiganting the ugly fonts problem in opensuse 10.2 I replaced first freetype 2.1 with freetype 2.2 in opensuse 10.0, so I learned that the problem was not in freetype. Later I replaced /etc/fonts in opensuse 10.2 with the one in opensuse 10.0. Then, full hinted fonts were beautiful again AND hinting in gtk apps worked as expected (warning, doing so make apps to take ages to load). -- 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=227498 jpr@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |federico@novell.com |gnome@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=227498 ------- Comment #11 from mfabian@novell.com 2007-02-14 13:34 MST ------- In your screen shots in comment #1 and comment #2 you can clearly see that full hinting is used in the menu bar of Seamonkey when the hinting is set to full. So what is the problem? -- 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=227498 ------- Comment #12 from mfabian@novell.com 2007-02-14 13:59 MST ------- Felix Miyata> URL is page displayed in SeaMonkey in the Felix Miyata> screenshots. SeaMonkey for those screenshots has been Felix Miyata> set to DejaVu Sans Condensed (same as the KDE desktop Felix Miyata> setting) as preference default. “DejaVu Sans Condensed” has no byte code instructions at all. Therefore it doesn't render well with the byte code interpreter. You get somewhat better rendering results with <match target="font"> <test name="family"> <string>DejaVu Sans Condensed</string> <edit name="autohint"> <bool>true</bool> </edit> </match> for that font, *but* on the cost of completely messed up spacing in the digits, see bug #215602. See also the following comment I wrote into /etc/fonts/suse-hinting.conf: <!-- Switch on the autohinter for a few TrueType fonts which have no byte code or very bad byte code and look better with the autohinter: But see also bug #215602 for many fonts the autohinter seriously distorts the metrics so badly that even the digits which should be monospaced are not monospaced at all anymore. Because of this problem, better don't switch on the autohinter for Sazanami IPA DejaVu Sans Light DejaVu Sans Condensed DejaVu Serif Condensed FreeSans FreeSerif FreeMono and other fonts with similar problems until this is solved in the autohinter. --> If there hadn't been the spacing problem from bug #215602, I would have switched on the autohinter for “DejaVu Sans Condensed”. But that spacing problem is also very nasty. If that spacing problem doesn't worry you, you may switch on the autohinter for “DejaVu Sans Condensed”. You can also try to switch on the autohinter for all fonts with <match target="font"> <edit name="autohint"> <bool>true</bool> </edit> </match> But it is really a pity to do that for fonts which have good byte code, with the autohinter they are much more blurry. Look at the font in the menu bar of your Seamonkey screen shots with full hinting: This is a font which has very good byte code and renders very sharp with full hinting and with the autohinter disabled (autohinter disabled means the byte code interpreter is used if it is compiled into freetype). Using the autohinter for a font with such good byte code throws away all the hard work the font designers did put into the byte code. -- 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=227498 ------- Comment #13 from mfabian@novell.com 2007-02-14 14:14 MST ------- Felix Miyata> 2-note spindly looking menu fonts What you see there is just the byte code interpreter working as intended. If you really want your fonts blurry, turn on the autohinter in your ~/.fonts.conf by inserting the snippet I already wrote above: <match target="font"> <edit name="autohint"> <bool>true</bool> </edit> </match> Felix Miyata> Actual behavior: Felix Miyata> 1-with hinting set to full hinting is off Felix Miyata> 2-with hinting set to none hinting is maximum No, that's not true, apparently you are just not used to how fonts look with the byte code interpreter. -- 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=227498 ------- Comment #14 from mfabian@novell.com 2007-02-14 14:43 MST ------- Please note that setting the hintstyle to hintslight forces the use of the autohinter instead of the byte code interpreter. See: http://lists.gnu.org/archive/html/freetype-devel/2007-01/msg00067.html -- 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=227498 ------- Comment #15 from mfabian@novell.com 2007-02-14 15:37 MST ------- A simple check to see whether a font has any byte code at all (using fontforge): mfabian@magellan:~$ fontforge -c 'Open("/usr/share/fonts/truetype/DejaVuSansCondensed.ttf");Save("/tmp/font.sfd")' Copyright (c) 2000-2006 by George Williams. Executable based on sources from 11:29 20-Dec-2006. mfabian@magellan:~$ grep -c TtfInstrs /tmp/font.sfd 0 mfabian@magellan:~$ fontforge -c 'Open("/usr/share/fonts/truetype/DejaVuSans.ttf");Save("/tmp/font.sfd")' Copyright (c) 2000-2006 by George Williams. Executable based on sources from 11:29 20-Dec-2006. mfabian@magellan:~$ grep -c TtfInstrs /tmp/font.sfd 828 mfabian@magellan:~$ Of course that doesn't tell you anything about the quality or usefulness of the byte code instructions. But you can see that DejaVuSansCondensed.ttf has no byte code instructions at all and will therefore most likely render better with the autohinter although this will cause the bugs with the spacing mentioned above. -- 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=227498 ------- Comment #16 from mfabian@novell.com 2007-02-14 15:58 MST ------- Created an attachment (id=119276) --> (https://bugzilla.novell.com/attachment.cgi?id=119276&action=view) dejavu-sans-and-dejavu-sans-condensed-with-and-without-autohinter.png Screen shots comparing rendering with autohinter versus byte code interpreter for “Dejavu Sans” and “DejaVu Sans Condensed”. The screen shots have been created with ftview -r 120 8 /usr/share/fonts/truetype/DejaVuSans.ttf ftview -r 120 8 /usr/share/fonts/truetype/DejaVuSansCondensed.tt Then in ftview hit ‘f’ to force autohinting. The two screen shots at the top are DejaVu Sans, the two screen shots at the bottom are DejaVu Sans Condensed. The screen shots at the left are using the byte code interpreter, the screen shots at the right are using the autohinter. You see that in case of DejaVu Sans the rendering with the byte code interpreter (top left screen shot) is less blurry. There is byte code and it works. You can easily spot the glyps which don't have byte code in this screen shot, they look much bolder and blurrier compared to the glyphs which have byte code. These are rarely used glyphs where nobody had time to create byte code yet. The top right screen shot, DejaVu Sans with the autohinter is overall a lot blurrier than with the byte code interpreter. But the blurriness is of course the same for all glyphs, there is no difference between glyphs with byte code and glyphs without byte code when the autohinter is used. The bottom left screen shot, DejaVu Sans Condensed is blurry because the byte code interpreter is used but there is no byte code available in the font. That means that no hinting whatsoever is used. Compared to that, the bottom right screen shote, DejaVu Sans Condensed with the autohinter looks sharper and less blurry. But as I said above, this causes a lot of spacing problems. You can see that the hinting has a big influence on the spacing by looking at the line breaks in the screen shots. The screen shots on the left (byte code interpreter) have the linebreaks at different glyphs than the screen shots on the right (auto hinter). -- 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=227498 mfabian@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Comment #17 from mfabian@novell.com 2007-02-14 16:02 MST ------- I'm closing the bug as INVALID now because it is not true at all that "full and none hinting selections are reversed in GTK apps" as was reported. I hope I have explained clearly enough what happens and how you can tune the setup according to your preferences if you don't like the defaults. -- 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