Dan Nicholson wrote:
On 3/24/06, Dan Nicholson <[EMAIL PROTECTED]> wrote:
It's time to finally finish this off.
OK, here's the first cut. All comments are welcome, from the
technical type to the typo/formatting type. There are surely errors
in here. CC'ing Alexander to make sure he sees this.
Next time please use my ums.usu.ru address. The linuxfromscratch.org address
is only for noise that Bugzillas create.
+ <para>The core X font protocol finds fonts from the server configuration
+ file (xorg.conf or XF86Config) in addition to an internal hard-coded
+ path. Assuming the prefix for your X installation is
There is no internal hardcoded path in effect. What is hardcoded is a font
path used when there is absolutely no font path configured in xorg.conf.
+ <para>Xft provides antialiased font rendering through
+ <application>Freetype</application>, and fonts are controlled from the
+ client side using <application>Fontconfig</application>. The default
+ search path is <filename class="directory">/usr/share/fonts</filename>
+ and <filename class="directory">~/.fonts</filename>.
+ When installing <application>X</application>, symlinks were created from
+ the <filename class="directory">OTF</filename> and <filename
+ class="directory">TTF</filename> <application>X</application> font
+ directories to <filename
+ class="directory">/usr/share/fonts/X11-{OTF,TTF}</filename>. This was
+ because we only want <application>Fontconfig</application> to use
+ scalable fonts and not others such as bitmapped or Type1 fonts.</para>
Type1 fonts are scalable. One can use Type1 fonts with fontconfig. It's just
the Type1 fonts coming with Xorg that are better excluded.
+ <para>Ensure that the Xft system will be loaded in 'XF86Config' or
+ 'xorg.conf'. The "Module" section should look like:</para>
- <sect3>
- <title>Ensure TrueType is Loaded in 'XF86Config' or 'xorg.conf'</title>
-
- <para>The "Module" section should look like:</para>
-
<screen><literal>Section "Module"
...
Load "freetype"
This is completely irrelevant. The "freetype" module is used for
non-antialiased rendering of TrueType and Type1 fonts via the core X font
protocol.
+ <para><application>Fontconfig</application>searches directories in its
+ path recursively and maintains a cache of the font characteristics in
+ <filename>fonts.cache-1</filename> files in each directory. This cache
+ can be regenerated using the <command>fc-cache</command> command at any
+ time.</para>
If the cache appears to be out of date, it is ignored, and information is
(slowly) fetched from the fonts themselves.
+ <para><ulink
+ url="http://osdn.dl.sourceforge.jp/efont/4845/";>Kochi fonts</ulink> -
Please replace the link: http://sourceforge.jp/projects/efont/
+ <para><ulink
+ url="http://kldp.net/frs/download.php/1429/baekmuk-ttf-2.2.tar.gz";>Baekmuk
fonts</ulink>
http://kldp.net/projects/baekmuk/
The rest is good (but please run a spellchecker). The following is, IMHO, a
wiki material, but you can put it into the book too.
Arphic fonts look blurry at small sizes. The FireFly font can be configured
to look sharper due to the use of the optimized embedded bitmaps present in
this font (but Fontconfig doesn't use them by default).
First, teach Fontconfig to prefer this font as a candidate for Monospace and
other generic aliases:
sed -i -e 's,^\(\t\t\t<family>Kochi.*\)$$,\1\n\t\t\t<family>AR PL New
Sung</family>,' /etc/fonts/fonts.conf
Then, tell Fontconfig to use the embedded bitmaps for font sizes that really
have such bitmaps, by adding this to /etc/fonts/local.conf or fonts.conf:
<match target="font">
<test name="family">
<string>AR PL New Sung</string>
</test>
<test name="pixelsize" compare="less_eq">
<double>16.0</double>
</test>
<test name="pixelsize" compare="more_eq">
<double>11.0</double>
</test>
<edit name="antialias" mode="assign">
<bool>false</bool>
</edit>
</match>
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
