Here is another variant. Get it here:
Hi. Due to business elsewhere, I just now checked in and, at this time, there's 4 replies plus my original, which equals 5 posts. And this post right here now makes a total of 6 posts so far.
(per above quote) I just wget'ed the diff.gz file.
There, you can see the (and also my customized contents) contents of the patches/source/freetype folder (I later renamed the folder to freetype234).
Before I wget'ed the mentioned diff.gz file, I (as it's seen above) renamed the original to "freetype.bytecode.interpreter_slack_orig.diff.gz"
Then I merely wget'ed the replacement into this folder.
I then (as it's seen above) made a copy of freetype.SlackBuild named freetype_ac.SlackBuild
I then edited and saved the change on that latter file, did enabled the bytecode interpreter line.
Next, I ran ./freetype_ac.SlackBuild
And it compiled, built a package.
I then renamed that package from: freetype-2.3.4-i486-1_slack11.0.tgz to freetype-2.3.4-i486-1_ac.tgz
# removepkg freetype-2.1.9-i486-1_ac.tgz
# installpkg freetype-2.3.4-i486-1_ac.tgz
I then logged out of KDE which reverts me back to run level 3 and into the first or logon terminal.
The fonts are now better yet than they ever were before (they were pretty darn good with freetype 2.1.9).
Linux fonts have been so good for a while now that it may now be a mute point to 1. add in msttf (ms true type fonts) and to 2. do this bytecode interpreter enabling thing.
But I'm not touching my fonts (since they're working so good at this time) as in "if it ain't broke, don't fix it."
As a guess, I'd guess that instead of my wget'ing that diff.gz file, I, instead, could have copied the contents as shared (next to the wget url) and then pasted that into an editor and then save it as a file named: freetype.bytecode.interpreter.diff
And then gzip that file so as to end up with: freetype.bytecode.interpreter.diff.gz
Another guess: I guess that's called a patch? Can someone confirm?
Lastly, can anyone share a good www site on the (very) basics or getting started learning of patch?
I guess (in a nutshell) a patch applies a diff to a former (or a pre existing) file during the compiling. Thus, this is a way of "on the fly" (or dynamically so to speak) obtaining an updated or altered outcome during the compiling. (am I correct here, on what I said in this paragraph?).