According to FreeType.org The TrueType bytecode patents have expired!

Does this mean we can modify freetype.SlackBuild to take advantage of it?
Original scripts it still commented out that patented part of code.

You don't need to since its automatically enabled in the 2.4 versions.

The latest version of my guide is in beta and at a new location:

http://duganchen.ca/writings/slackware/fonts

The biggest change is that I'm discontinuing the patched packages. Instead, I'm now providing step-by-step instructions to either enable the default Freetype subpixel renderer, or to apply the infinality.net patches.

Comments please.

The old version is still at http://www.vcn.bc.ca/~dugan/slackware-fonts/index.html and will remain online for another day or so.

2 members found this post helpful.

Hi,

Dugan, do you think it would be possible to keep the older version available? Loads of people are still using older versions of Slackware. Great guide!

I just realized that in my $HOME/.Xdefaults file, I made mistake of using xft*dpi: 96 instead Xft*dpi: 96.0 after correct this problem my font is start looking good. Nonetheless, I recompiled freetype.SlackBuild with uncommenting old patented code.

Okay, I've added back what I think would still be useful to people using older Slackware versions:

• the Freetype, Fontconfig and Cairo SlackBuilds
• the location of the xdm Xservers file in 13.1

If I missed something else, then please specify it.

I will not keep the older version online.

I noticed in your new version that the first line in your .Xdefaults was "Xft.antialias: 1" whereas your older version of the guide listed as "! Xft.antialias: 1". Which one is correct?

That is not a matter of correctness but rather a matter of opinion. These days, I have it uncommented.

A suggestion - it would be great if you could include screenshots displaying rendering using:
1. Default font rendering
2. Your method (Ubuntu rendering)
3. Infinality rendering

It will help the uninitiated decide on a method.

Offtopic: I myself use infinality, but have never tried your Ubuntu rendering. Do you prefer infinality over your ubuntu style rendering?

@Daedra, couple of questions:
1. Is this order for building the packages or for installing the newly compiled/built packages?
2. Is the order _really_ required?

Screenshots are good idea, but I think I've already provided enough information to decide on a method:

• default subpixel rendering is the default choice
• Infinality rendering if you're using a font collection that you got from a Windows or OS X installation (and I mean the entire c:\windows\fonts directory, not just a Linux corefonts package).
• Ubuntu rendering if you're using an older version of Slackware (because I didn't update the SlackBuilds for 13.37)

Hello,
First I want to thank you for a wonderfull guide And also I would like to ask if you could clarify this:
It is dificult for me too find where is this "between the and tags"

Thanks for catching that. I fixed it. It should have said "the <fontconfig> and </fontconfig> tags".

@dugan

Hi, in your new tutorial (thanks btw), and particularly your infinality instructions, you mention this:
"As you would to get the default subpixel renderer, edit Freetype’s SlackBuild.
Only now, add the following patch lines in what I hope is the obvious place:"

Because, English is not my first language, I just need to clarify something. To get the infinality setup, besides adding the three infinality lines to the slackbuild, do I have to also uncomment the line "zcat..." ?

I'm asking this because I used the arch infinality package on my Arch system (I don't use arch anymore, to really compare), but on Slackware I'm experiencing some weird red colorizations on my fonts occasionally.

mmm.. got to try this patch!!