https://bugzilla.novell.com/show_bug.cgi?id=393748 User mfabian@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393748#c16 Mike Fabian <mfabian@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |INVALID --- Comment #16 from Mike Fabian <mfabian@novell.com> 2008-05-26 12:18:03 MDT --- Felix Miyata> Created an attachment (id=218174) --> (https://bugzilla.novell.com/attachment.cgi?id=218174) [details] Felix Miyata> screenshot on Max 0S X Felix Miyata> Felix Miyata> This is same URL as used for attachment 217621 [details] Felix Miyata> taken of Safari 3.1.1. Note for the fonts actually Felix Miyata> installed how similar they are to Opera, SeaMonkey, Felix Miyata> Konq3 & Epiphany, and how much different from FF3, with Felix Miyata> hinting medium, and regardless whether albw.ttf and/or Felix Miyata> arial.ttf are installed. This is how I prefer all my Felix Miyata> fonts to look, because they carry enough stroke weight Felix Miyata> to actually see. Whether they are properly characterized Felix Miyata> as byte code interpreted, anti-aliased, unenhanced or Felix Miyata> anything else is irrelevant to me. This Mac OS X screenshot is without subpixel hinting (contrary to the "Cleartype" screenshots where you can clearly see the colours (magnify if you don’t see it!)). This hintstyle is a lot bolder and blurrier than using byte code hinting. You can come closest to this style on openSUSE by using the autohinter with full or medium hinting, antialiasing on and subpixel hinting off. I.e. the following settings in ~/.fonts.conf: <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="autohint" > <bool>true</bool> </edit> </match> <match target="font" > <edit mode="assign" name="hintstyle" > <const>hintfull</const> (or hintmedium here) </edit> </match> <match target="font" > <edit mode="assign" name="antialias" > <bool>true</bool> </edit> </match> I think this is far uglier than the sharpness achieved by the byte code interpreter. But tastes differ. I have to close this as INVALID because there is nothing wrong with Arial/Albany AMT in the path. They just happen to have good byte code and are rather small at the default point size. There’s nothing wrong with that. And there is no difference how Konqueror and Firefox handle these, if you use the same hinting settings, both will render them the same way. It is not nice that KDE/Gnome set this differently (KDE writes to ~/.fonts.conf and Gnome sets X-Resources) but you can still achieve the same look and feel if you use equivalent settings for both desktops. Neither of the desktops currently has an option to use the byte code interpreter, i.e. <match target="font" > <edit mode="assign" name="autohint" > <bool>false</bool> </edit> </match> in your ~/.fonts.conf or the autohinter, i.e. <match target="font" > <edit mode="assign" name="autohint" > <bool>true</bool> </edit> </match> (byte code interpreter must be compiled into freetype2 otherwise autohint=false will look terribly blurry. The byte code interpreter is compiled into freetype2 by default on openSUSE). That the desktops set this in different ways and if you set it up in KDE it doesn’t automatically use the same settings in Gnome and vice versa is not nice. This should be improved in the future, currently I recommend to set equivalent settings manually in both desktops. -- 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.