Talk:Fontconfig

Infinality patches
Regarding Infinality: the patches are not yet in Portage so there's nothing to write about them, also author of this article is rather doubting the point of them since pretty much all font nerds consider autohinter to be the omitted for the sake of decency and, even if that has changed, author failed to find any images of direct vanilla vs. full Infinality comparison and all the other images look, frankly, bad. Anyway, the Infinality patch that adds incomplete ClearType (an MS sub-pixel rendering technology) support was recently accepted by upstream and will be available with the next freetype version. — Nfk, 3 July 2012 (note moved from main page to discussion page by yngwin)


 * I am intending to get the Infinality patches into the portage tree. They are currently available in an overlay . — yngwin 15:14, 3 July 2012 (UTC)
 * That's not even an official overlay lest one of the few I`m using. *sigh* Anyway, I recommend making some comparison screenshots to understand if there's any point to Infinality, especially the autohinter part. Oh, and I found official examples which even more so make me wonder about it, in particular Infinality Times New Roman is so much worse than my vanilla hintfull RGB sub-pixel hinting with default lcdfilter that you have to wonder if it`s not some mistake or an old work in progress screenshot. Sadly I can't post my screenshot because Ksnapshot seesm to mess up colors and possibly fonts themselves making them blurrier than in reality. Nfk 16:27, 3 July 2012 (UTC)

After some weeks (I really have lost track of time) of testing, the only thing I can say is that at the moment on Gentoo Infinality is almost non-deterministic - the only known thing is that it almost always affects how fonts are rendered and I guess for the better but the way it does it is random even between install-purge-install cycles with supposedly the same configuration. It appears that it may even crash some applications. Also similar reports can be found on their official forum where even the supported Fedora 17 systems exhibit seemingly random behaviour. If you want Infinality, for now stick to Ubuntu (it has Infinality, right?) or brace yourself for some Sanity Points culling experience. — The preceding unsigned comment was added by Nfk (talk • contribs) 15 August 2012
 * Forgot to mention that eselect-infinality and eselect-lcdfilter are also acting weirdly
 * — The preceding unsigned comment was added by Nfk (talk • contribs) 15 August 2012

Some chars(or what they're called, code points?) don't display correctly
For example these 3 chars "𝙵𝟢𝟢" which should look like "FOO" only display when media-fonts/noto or (not recommended) media-fonts/unifont are installed. It seems to me that even though the main font in qterminal or xfce4-terminal is say Cousine 11 or Inconsolata 11 or Misc Fixed 11 or Monospace, those 3 FOO-like chars always appear the same, as if the current font doesn't have a way to show them so they fall back to a font that does (in my case 'noto'). I'm only guessing this is the case, but whatever.... Point is, an extra font was needed to avoid seeing either spaces, or squares, or squares with hex numbers within them instead of that "𝙵𝟢𝟢". Wellillbe (talk) 11:04, 10 May 2021 (UTC)

Section Using sub-pixel rendering - Removed warning about patenting issues and it's fix with the bindist flag on the package freetype
I removed the warning section regarding the flag bindist since it doesn't appear anymore; at least not in version media-libs/freetype-2.12.1-r1

I was trying to find any documentation about the original warning, any change in the projects state or any mention about the patent issues but I couldn't find anything, if somebody can find something regarding that fact, it may be important to revert the change and to reinstate the flag on the package.

--Patomas (talk) 01:22, 20 October 2022 (UTC)