You are not logged in.
Hi,
I have always admired Ubuntu for its font rendering; the best of any operating system in my opinion. This was largely due to the lcdfilter patch, and although this was present in Arch there were some subtle differences. Hence I have been using freetype2-ubuntu, fontconfig-ubuntu and cairo-ubuntu from AUR for some time.
Just recently, I have noticed that these differences are no more. I see identical (i.e. very nice) rendering when using the stock freetype2, fontconfig and cairo packages from the default repositories. I haven't done an A/B comparison against every single font on my system of course, but I wondered if anyone has a view on the -ubuntu packages and whether they still serve any purpose?
Thanks.
Wirth's law: "Software is getting slower more rapidly than hardware becomes faster"
Offline
:: Registered Linux User No. 223384
:: github
:: infinality-bundle+fonts: good looking fonts made easy
Offline
I believe some of the infinality patches were merged into freetype recently.
edit: yep, the changelog in bohoomil's link confirms that.
I still use freetype2-infinality and fontconfig-infinality from the aur though, because infinality's fontconfig is awesome ![]()
Last edited by bwat47 (2013-04-15 14:48:22)
Offline
But bohoomil's link also tells that the autohinting feature has to be applied explicitely using a configure switch. I do not see that in freetype's official PKGBUILD.
Offline
Ubuntu fontconfig is still better than freetype2 from official arch repos. A lot of stuff from infinality is yet to be merged into freetype2.
Still I would reckon infinality AUR is way way better than ubuntu fontconfig.
Offline
Still I would reckon infinality AUR is way way better than ubuntu fontconfig.
That's right, because Infinality patches make it possible to tune individual aspects of font's rendering (via /etc/profile/infinality-settings.sh) and apply highly customized rules to font groups depending on their characteristics (via dedicated fontconfig files) rather than a fixed set of instructions globally to all fonts.
But bohoomil's link also tells that the autohinting feature has to be applied explicitely using a configure switch. I do not see that in freetype's official PKGBUILD.
As far as I can tell, this has nothing to with autohinting (which does something else), but subpixel rendering enabled via freetype-2.3.0-enable-spr.patch. While my assumption was not entirely correct, FT_CONFIG_OPTION_SUBPIXEL_RENDERING seems to have been initially enabled only in freetype2 version 2.4.11.
Last edited by bohoomil (2013-04-15 18:46:34)
:: Registered Linux User No. 223384
:: github
:: infinality-bundle+fonts: good looking fonts made easy
Offline
fontconfig is still better than freetype2
Huh? That makes no sense. It's like saying a Porsche is better than a garage. Say what?!
Offline
Sorry. Honest mistake.
It should have been freetype2 vs freetype2-ubuntu.
Offline
Thanks for the info guys. I should have found that myself, had I consulted the upstream release notes - sorry. The "lcdfilter" Xft parameter has been effective for a long time when using the standard packages, but it didn't match the look of the -ubuntu packages until now. I assume this is the effect of "subpixel hinting support".
When I used Fedora, there was a package in rpmfusion named "freetype-freeworld" with this patch. I don't suppose this is needed any more.
Wirth's law: "Software is getting slower more rapidly than hardware becomes faster"
Offline
Arch isn't enabling subpixel hinting support with the current package. That's not what you're seeing.
Offline
Arch isn't enabling subpixel hinting support with the current package. That's not what you're seeing.
Interesting, thanks. One thing I really should have mentioned is that I use the same /etc/fonts/local.conf file now that I have always used:
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
<match target="font">
<edit name="antialias" mode="assign">
<bool>true</bool>
</edit>
</match>
<match target="font">
<edit name="hinting" mode="assign">
<bool>true</bool>
</edit>
</match>
<match target="font">
<edit name="autohint" mode="assign">
<bool>false</bool>
</edit>
</match>
<match target="font">
<edit name="hintstyle" mode="assign">
<const>hintslight</const>
</edit>
</match>
<match target="font">
<edit name="rgba" mode="assign">
<const>rgb</const>
</edit>
</match>
<match target="font">
<edit mode="assign" name="lcdfilter">
<const>lcddefault</const>
</edit>
</match>
</fontconfig>With the latest freetype2, fontconfig and cairo packages from [extra] I see a Ubuntu-like result (A/B compare between two VMs, one with the equivalent *-ubuntu packages from AUR). It used to be very close (slightly darker glyphs?) but now it's identical to my eyes.
Thanks everyone for your replies, I've since had another look at the *-infinality packages from AUR and enjoying playing with the settings. These do give some very nice results! Font rendering is one of those things I probably obsess about far too much, but it can make a Linux desktop so nice to use I stopped wanting a Mac several years ago.
Last edited by Modeler (2013-04-19 09:15:29)
Wirth's law: "Software is getting slower more rapidly than hardware becomes faster"
Offline
I use the same /etc/fonts/local.conf file now that I have always used
So? I think there's a very important point that's being missed: To look their best, a lot of fonts need fontconfig entries on an individual basis, and then possibly further tweaked for e.g. differences sizes and boldness.
There's an example in my sig. Bigger examples are infinality and bohoomil.
Offline