<!doctype LINUXDOC PUBLIC "-//Xorg//DTD linuxdoc//EN" [
<!ENTITY % defs SYSTEM "defs.ent"> %defs;
]>

<article>

<title>Fonts in X11R&relvers;
<author>Juliusz Chroboczek, <email/jch@pps.jussieu.fr/
<date>25 March 2004</date>

<ident>
</ident>

<toc>

<sect>Introduction

<p>This document describes the support for fonts in X11R&relvers;.  <ref
id="sec:installing" name="Installing fonts"> is aimed at the 
casual user wishing to install fonts in X11R&relvers; the rest of the
document describes the font support in more detail.

We assume some familiarity with digital fonts.  If anything is not
clear to you, please consult <ref id="sec:background"
name="Appendix: Background"> at the end of this document for background
information.

<sect1>Two font systems

<p>X includes two font systems: the original core X11 fonts system, which
is present in all implementations of X11, and the Xft fonts system,
which may not be distributed with implementations of X11 that
are not based on X11R&relvers; but will hopefully be included by them in
the future

The core X11 fonts system is directly derived from the fonts system
included with X11R1 in 1987, which could only use monochrome bitmap
fonts.  Over the years, it has been more or less happily coerced into
dealing with scalable fonts and rotated glyphs.

Xft was designed from the start to provide good support for scalable
fonts, and do so efficiently.  Unlike the core fonts system, it
supports features such as anti-aliasing and sub-pixel rasterisation.
Perhaps more importantly, it gives applications full control over the
way glyphs are rendered, making fine typesetting and WYSIWIG display
possible.  Finally, it allows applications to use fonts that are not
installed system-wide for displaying documents with embedded fonts.

Xft is not compatible with the core fonts system: usage of Xft
requires making fairly extensive changes to toolkits (user-interface
libraries).  While X.org will continue to maintain the core fonts
system, toolkit authors are encouraged to switch to Xft as soon as
possible.

<sect>Installing fonts<label id="sec:installing">

<p>This section explains how to configure both Xft and the core fonts
system to access newly-installed fonts.

<sect1>Configuring Xft<label id="sec:configuring-xft">

<p>Xft has no configuration mechanism itself, rather it relies upon
the fontconfig library to configure and customize fonts.  That library
is not specific to X11R&relvers; or indeed on any particular font output
mechanism.  This discussion describes how fontconfig, rather than Xft,
works.

<sect2>Installing fonts in Xft

<p>Fontconfig looks for fonts in a set of well-known directories that
include all of X11R&relvers;'s standard font directories
(`<tt>/usr/X11R6/lib/X11/lib/fonts/*</tt>') by default) as well as a
directory called `<tt>.fonts/</tt>' in the user's home directory.
Installing a font for use by Xft applications is as simple
as copying a font file into one of these directories.
<tscreen><verb>
$ cp lucbr.ttf ~/.fonts/
</verb></tscreen>
Fontconfig will notice the new font at the next opportunity and rebuild its
list of fonts.  If you want to trigger this update from the command
line (for example in order to globally update the system-wide Fontconfig
information), you may run the command `<tt/fc-cache/'.
<tscreen><verb>
$ fc-cache
</verb></tscreen>

<sect2>Fine-tuning Xft

<p>Fontconfig's behaviour is controlled by a set of configuration files: a
system-wide configuration file, `<tt>/etc/fonts/fonts.conf</tt>', and
a user-specific file called `<tt>.fonts.conf</tt>' in the user's home
directory (this can be overridden with the `<tt/FONTCONFIG_FILE/'
environment variable).

Every Fontconfig configuration file must start with the following
boilerplate:
<tscreen><verb>
&lt;?xml version="1.0"?&gt;
&lt;!DOCTYPE fontconfig SYSTEM "fonts.dtd"&gt;
&lt;fontconfig&gt;
</verb></tscreen>
In addition, every Fontconfig configuration file must end with the
following line:
<tscreen><verb>
&lt;/fontconfig&gt;
</verb></tscreen>

The default Fontconfig configuration file includes the directory
`<tt>~/.fonts/</tt>' in the list of directories searched for font
files, and this is where user-specific font files should be installed.
In the unlikely case that a new font directory needs to be added, this
can be done with the following syntax:
<tscreen><verb>
&lt;dir&gt;/usr/local/share/fonts/&lt;/dir&gt;
</verb></tscreen>

Another useful option is the ability to disable anti-aliasing (font
smoothing) for selected fonts.  This can be done with the following
syntax:
<tscreen><verb>
&lt;match target="font"&gt;
    &lt;test qual="any" name="family"&gt;
        &lt;string&gt;Lucida Console&lt;/string&gt;
    &lt;/test&gt;
    &lt;edit name="antialias" mode="assign"&gt;
        &lt;bool&gt;false&lt;/bool&gt;
    &lt;/edit&gt;
&lt;/match&gt;
</verb></tscreen>
Anti-aliasing can be disabled for all fonts by the following incantation:
<tscreen><verb>
&lt;match target="font"&gt;
    &lt;edit name="antialias" mode="assign"&gt;
        &lt;bool&gt;false&lt;/bool&gt;
    &lt;/edit&gt;
&lt;/match&gt;
</verb></tscreen>

Xft supports sub-pixel rasterisation on LCD displays.  X11R&relvers; should
automatically enable this feature on laptops and when using an LCD
monitor connected with a DVI cable; you can check whether this was
done by typing
<tscreen><verb>
$ xdpyinfo -ext RENDER | grep sub-pixel
</verb></tscreen>
If this doesn't print anything, you will need to configure Render for
your particular LCD hardware manually; this is done with the following
syntax:
<tscreen><verb>
&lt;match target="font"&gt;
    &lt;edit name="rgba" mode="assign"&gt;
        &lt;const&gt;rgb&lt;/const&gt;
    &lt;/edit&gt;
&lt;/match&gt;
</verb></tscreen>
The string `<tt/rgb/' within the
`<tt/&lt;const&gt;/'...`<tt>&lt;/const&gt;</tt>'
specifies the order of pixel components on your display, and should be
changed to match your hardware; it can be one of `<tt/rgb/ (normal
LCD screen), `<tt/bgr/' (backwards LCD screen), `<tt/vrgb/' (LCD
screen rotated clockwise) or `<tt/vbgr/' (LCD screen rotated
counterclockwise).

<sect2>Configuring applications

<p>Because most current applications use the core fonts system by
default, it is necessary to explicitly configure them to use Xft.
How this is done depends on the application.

XTerm can be set to use Xft by using the `<tt/-fa/' command line
option or by setting the `<tt/XTerm*faceName/' resource:
<tscreen><verb>
XTerm*faceName: Courier
</verb></tscreen>
or
<tscreen><verb>
$ xterm -fa "Courier"
</verb></tscreen>

For applications based on GTK+ 2.0 (including GNOME 2 applications),
the environment variable `<tt/GDK_USE_XFT/' should be set to `<tt/1/':
<tscreen><verb>
$ export GDK_USE_XFT=1
</verb></tscreen>

GTK+ 2.2 uses Xft by default.

For KDE applications, you should select ``Anti-alias fonts'' in the
``Fonts'' panel of KDE's ``Control Center''.  Note that this option is
misnamed: it switches KDE to using Xft but doesn't enable
anti-aliasing in case it was disabled by your Xft configuration file.

<it>(What about Mozilla?)</it>

<sect2>Troubleshooting <label id="sec:troubleshooting-xft">

<p>If some Xft-based applications don't seem to notice the changes you
are making to your configuration files, they may be linked against an
old version of Xft.  In order to fix the problem, you should
relink them against a current version of Xft; on most systems, it is
enough to install the current version of the Xft and Fontconfig
libraries.

If, for some reason, you cannot upgrade the shared libraries, please
check the <htmlurl name="Xft(3)" url="Xft.3.html"> manual page included
with XFree86 4.2 for the configuration mechanisms of the previous version
of Xft.

<sect1>Configuring the core X11 fonts system

<p>Installing fonts in the core system is a two step process.  First,
you need to create a <it/font directory/ that contains all the
relevant font files as well as some index files.  You then need to
inform the X server of the existence of this new directory by
including it in the <it/font path/.

<sect2>Installing bitmap fonts

<p>The X11R&relvers; server can use bitmap fonts in both the cross-platform
BDF format and the somewhat more efficient binary PCF format.
(X11R&relvers; also supports the obsolete SNF format.)

Bitmap fonts are normally distributed in the BDF format.  Before
installing such fonts, it is desirable (but not absolutely necessary)
to convert the font files to the PCF format.  This is done by using the
command `<tt/bdftopcf/', <it/e.g./ 
<tscreen><verb>
$ bdftopcf courier12.bdf
</verb></tscreen>
You will then want to compress the resulting PCF font files:
<tscreen><verb>
$ gzip courier12.pcf
</verb></tscreen>

After the fonts have been converted, you should copy all the font
files that you wish to make available into a arbitrary directory, say
`<tt>/usr/local/share/fonts/bitmap/</tt>'.  You should then create the
index file `<tt/fonts.dir/' by running the command `<tt/mkfontdir/'
(please see the <htmlurl name="mkfontdir(1)" url="mkfontdir.1.html">
manual page for more information):
<tscreen><verb>
$ mkdir /usr/local/share/fonts/bitmap/
$ cp *.pcf.gz /usr/local/share/fonts/bitmap/
$ mkfontdir /usr/local/share/fonts/bitmap/
</verb></tscreen>

All that remains is to tell the X server about the existence of the
new font directory; see <ref id="sec:set-font-path" name="Setting the
server font path"> below.

<sect2>Installing scalable fonts

<p>The X11R&relvers; server supports scalable fonts in three formats:
Type&nbsp;1, TrueType and CIDFont.  This section only applies
to the first two; for information on CIDFonts, please see
<ref id="sec:cid-fonts" name="Installing CIDFonts"> later in this
document.   Previous versions also included support for the Speedo
scalable font format, but that is disabled in the default builds of
X11R6.9 and not included in X11R7.0 and later releases.

Installing scalable fonts is very similar to installing bitmap fonts:
you create a directory with the font files, and run `<tt/mkfontdir/'
to create an index file called `<tt/fonts.dir/'.

There is, however, a big difference: `<tt/mkfontdir/' cannot
automatically recognise scalable font files.  For that reason, you
must first index all the font files in a file called
`<tt/fonts.scale/'.  While this can be done by hand, it is best done
by using the `<tt/mkfontscale/' utility.
<tscreen><verb>
$ mkfontscale /usr/local/share/fonts/Type1/
$ mkfontdir /usr/local/share/fonts/Type1/
</verb></tscreen>
Under some circumstances, it may be necessary to modify the
`<tt/fonts.scale/' file generated by <tt/mkfontscale/; for more
information, please see the <htmlurl name="mkfontdir(1)"
url="mkfontdir.1.html"> and <htmlurl name="mkfontscale(1)"
url="mkfontscale.1.html"> manual pages and <ref
id="sec:internationalisation" name="Core fonts and internationalisation">
later in this document.

<sect2>Installing CID-keyed fonts <label id="sec:cid-fonts">

<p>The CID-keyed font format was designed by Adobe Systems for fonts
with large character sets.  A CID-keyed font, or CIDFont for short,
contains a collection of glyphs indexed by <it/character ID/ (CID).

In order to map such glyphs to meaningful indices, Adobe provide a set
of <it/CMap/ files.  The PostScript name of a font generated from a
CIDFont consists of the name of the CIDFont and the name of the CMap
separated by two dashes.  For example, the font generated from the
CIDFont `<tt/Munhwa-Regular/' using the CMap `<tt/UniKS-UCS2-H/' is
called
<tscreen><verb>
Munhwa-Regular--UniKS-UCS2-H
</verb></tscreen>

The CIDFont code in X11R&relvers; requires a very rigid directory
structure.  The main directory must be called `<tt/CID/' (its location
defaults to `<tt>/usr/X11R6/lib/X11/fonts/CID</tt>' but it may be
located anywhere), and it should contain a subdirectory for every CID
collection.  Every subdirectory <it/must/ contain subdirectories
called <tt/CIDFont/ (containing the actual CIDFont files), <tt/CMap/
(containing all the needed CMaps), <tt/AFM/ (containing the font
metric files) and <tt/CFM/ (initially empty).  For example, in the
case of the font <tt/Munhwa-Regular/ that uses the CID collection
<tt/Adobe-Korea1-0/, the directory structure should be as follows:
<tscreen><verb>
CID/Adobe-Korea1/CIDFont/Munhwa-Regular
CID/Adobe-Korea1/CMap/UniKS-UCS2-H
CID/Adobe-Korea1/AFM/Munhwa-Regular.afm
CID/Adobe-Korea1/CFM/
CID/fonts.dir
CID/fonts.scale
</verb></tscreen>

After creating this directory structure and copying the relevant
files, you should create a `<tt/fonts.scale/' file.  This file has the
same format as in the case of (non-CID) scalable fonts, except that
its first column contains PostScript font names with the extension
`<tt/.cid/' appended rather than actual filenames:
<tscreen><verb>
1
Adobe-Korea1/Munhwa-Regular--UniKS-UCS2-H.cid \
  -adobe-munhwa-medium-r-normal--0-0-0-0-p-0-iso10646-1
</verb></tscreen>
(both names on the same line).  Running `<tt/mkfontdir/'
creates the `<tt/fonts.dir/' file:
<tscreen><verb>
$ cd /usr/local/share/fonts/CID
$ mkfontdir
</verb></tscreen>

Finally, you should create the font metrics summary files in the
directory `<tt/CFM/' by running the command `<tt/mkcfm/':
<tscreen><verb>
$ mkcfm /usr/local/share/fonts/CID
</verb></tscreen>
If no CFM files are available, the server will still be able to use
the CID fonts but querying them will take a long time.  You should run
`<tt/mkcfm/' again whenever a change is made to any of the CID-keyed
fonts, or when the CID-keyed fonts are copied to a machine with a
different architecture.

<sect2>Setting the server's font path <label id="sec:set-font-path">

<p>The list of directories where the server looks for fonts is known
as the <it/font path/.  Informing the server of the existence of a new
font directory consists of putting it on the font path.

The font path is an ordered list; if a client's request matches
multiple fonts, the first one in the font path is the one that gets
used.  When matching fonts, the server makes two passes over the font
path: during the first pass, it searches for an exact match; during
the second, it searches for fonts suitable for scaling.

For best results, scalable fonts should appear in the font path before
the bitmap fonts; this way, the server will prefer bitmap fonts to
scalable fonts when an exact match is possible, but will avoid scaling
bitmap fonts when a scalable font can be used.  (The `<tt/:unscaled/'
hack, while still supported, should no longer be necessary in X11R&relvers;.)

You may check the font path of the running server by typing the command
<tscreen><verb>
$ xset q
</verb></tscreen>

<sect3>Temporary modification of the font path

<p>The `<tt/xset/' utility may be used to modify the font path for the
current session.  The font path is set with the command <tt/xset fp/;
a new element is added to the front with <tt/xset +fp/, and added to
the end with <tt/xset fp+/.  For example,
<tscreen><verb>
$ xset +fp /usr/local/fonts/Type1
$ xset fp+ /usr/local/fonts/bitmap
</verb></tscreen>

Conversely, an element may be removed from the front of the font path
with `<tt/xset -fp/', and removed from the end with `<tt/xset fp-/'.
You may reset the font path to its default value with 
`<tt/xset fp default/'.

For more information, please consult the <htmlurl name="xset(1)"
url="xset.1.html"> manual page.

<sect3>Permanent modification of the font path

<p>The default font path (the one used just after server startup or
after `<tt/xset fp default/') is specified in the X server's
`<tt/xorg.conf/' file.  It is computed by appending all the
directories mentioned in the `<tt/FontPath/' entries of the
`<tt/Files/' section in the order in which they appear.
<tscreen><verb>
FontPath "/usr/local/fonts/Type1"
...
FontPath "/usr/local/fonts/bitmap"
</verb></tscreen>

For more information, please consult the <htmlurl name="xorg.conf(5)"
url="xorg.conf.5.html"> manual page.

<sect2>Troubleshooting <label id="sec:troubleshooting-core">

<p>If you seem to be unable to use some of the fonts you have
installed, the first thing to check is that the `<tt/fonts.dir/' files
are correct and that they are readable by the server (the X server
usually runs as root, beware of NFS-mounted font directories).  If
this doesn't help, it is quite possible that you are trying to use a
font in a format that is not supported by your server.

X11R&relvers; supports the BDF, PCF, SNF, Type 1, TrueType, OpenType
and CIDFont font formats.  However, not all X11R&relvers; servers
come with all the font backends configured in.

On most platforms, the X11R&relvers; servers are <it/modular/: the font
backends are included in modules that are loaded at runtime.  The
modules to be loaded are specified in the `<tt/xorg.conf/' file using
the `<tt/Load/' directive:
<tscreen><verb>
Load "type1"
</verb></tscreen>
If you have trouble installing fonts in a specific format, you may
want to check the server's log file in order to see whether the
relevant modules are properly loaded.  The list of font modules
distributed with X11R&relvers; is as follows:
<itemize>
<item> <tt/"bitmap"/: bitmap fonts (`<tt/*.bdf/', `<tt/*.pcf/'
and `<tt/*.snf/');
<item> <tt/"freetype"/: TrueType fonts (`<tt/*.ttf/' and
`<tt/*.ttc/'), OpenType fonts (`<tt/*.otf/' and `<tt/*.otc/') and
Type&nbsp;1 fonts (`<tt/*.pfa/' and `<tt/*.pfb/');
<item> <tt/"type1"/: alternate Type&nbsp;1 backend (`<tt/*.pfa/' and
`<tt/*.pfb/') and CIDFont backend;
<item> <tt/"xtt"/: alternate TrueType backend (`<tt/*.ttf/' and
`<tt/*.ttc/').
</itemize>
Please note that the argument of the `<tt/Load/' directive is
case-sensitive.

<sect>Fonts included with X11R&relvers;

<sect1>Standard bitmap fonts

<p>The Sample Implementation of X11 (SI) comes with a large number of
bitmap fonts, including the `<tt/fixed/' family, and bitmap versions
of Courier, Times, Helvetica and some members of the Lucida family.  In
the SI, these fonts are provided in the ISO&nbsp;8859-1 encoding (ISO
Latin Western-European).

In X11R&relvers;, a number of these fonts are provided in Unicode-encoded
font files instead.  At build time, these fonts are split into font
files encoded according to legacy encodings, a process which allows
us to provide the standard fonts in a number of regional encodings
with no duplication of work.

For example, the font file
<tscreen><verb>
/usr/X11R6/lib/X11/fonts/misc/6x13.bdf
</verb></tscreen>
with XLFD
<tscreen><verb>
-misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso10646-1
</verb></tscreen>
is a Unicode-encoded version of the standard `<tt/fixed/' font with
added support for the Latin, Greek, Cyrillic, Georgian, Armenian, IPA
and other scripts plus numerous technical symbols.  It contains over
2800 glyphs, covering all characters of ISO&nbsp;8859 parts 1-5,
7-10, 13-15, as well as all European IBM and Microsoft code pages,
KOI8, WGL4, and the repertoires of many other character sets.

This font is used at build time for generating the font files
<tscreen><verb>
6x13-ISO8859-1.bdf
6x13-ISO8859-2.bdf
...
6x13-ISO8859-15.bdf
6x13-KOI8-R.bdf
</verb></tscreen>
with respective XLFDs
<tscreen><verb>
-misc-fixed-medium-r-normal--13-120-75-75-c-60-iso8859-1
...
-misc-fixed-medium-r-normal--13-120-75-75-c-60-iso8859-15
-misc-fixed-medium-r-normal--13-120-75-75-c-60-koi8-r
</verb></tscreen>
The standard short name `<tt/fixed/' is normally an alias for
<tscreen><verb>
-misc-fixed-medium-r-normal--13-120-75-75-c-60-iso8859-1
</verb></tscreen>

<sect1>The ClearlyU Unicode font family

<p>The ClearlyU family of fonts provides a set of 12&nbsp;pt,
100&nbsp;dpi proportional fonts with many of the glyphs needed for
Unicode text.  Together, the fonts contain approximately 7500 glyphs.

The main ClearlyU font has the XLFD
<tscreen><verb>
-mutt-clearlyu-medium-r-normal--17-120-100-100-p-101-iso10646-1 
</verb></tscreen>
and resides in the font file
<tscreen><verb>
/usr/X11R6/lib/X11/fonts/misc/cu12.pcf.gz 
</verb></tscreen>
Additional ClearlyU fonts include
<tscreen><verb>
-mutt-clearlyu alternate glyphs-medium-r-normal--17-120-100-100-p-91-iso10646-1 
-mutt-clearlyu pua-medium-r-normal--17-120-100-100-p-111-iso10646-1
-mutt-clearlyu arabic extra-medium-r-normal--17-120-100-100-p-103-fontspecific-0
-mutt-clearlyu ligature-medium-r-normal--17-120-100-100-p-141-fontspecific-0
</verb></tscreen>

The <it/Alternate Glyphs/ font contains additional glyph shapes that
are needed for certain languages.  A second alternate glyph font will
be provided later for cases where a character has more than one
commonly used alternate shape (<it/e.g./ the Urdu heh).

The <it/PUA/ font contains extra glyphs that are useful for certain
rendering purposes.

The <it/Arabic Extra/ font contains the glyphs necessary for
characters that don't have all of their possible shapes encoded in
ISO&nbsp;10646.  The glyphs are roughly ordered according to the order
of the characters in the ISO&nbsp;10646 standard.

The <it/Ligature/ font contains ligatures for various scripts that
may be useful for improved presentation of text.

<sect1>Standard scalable fonts

<p>X11R&relvers; includes all the scalable fonts distributed with X11R6.

<sect2>Standard Type&nbsp;1 fonts

<p>The IBM Courier set of fonts cover ISO&nbsp;8859-1 and
ISO&nbsp;8859-2 as well as Adobe Standard Encoding.  These fonts have
XLFD
<tscreen><verb>
-adobe-courier-medium-*-*--0-0-0-0-m-0-*-*
</verb></tscreen>
and reside in the font files
<tscreen><verb>
/usr/X11R6/lib/X11/fonts/Type1/cour*.pfa
</verb></tscreen>

The Adobe Utopia set of fonts only cover ISO&nbsp;8859-1 as well as
Adobe Standard Encoding.  These fonts have XLFD
<tscreen><verb>
-adobe-utopia-*-*-normal--0-0-0-0-p-0-iso8859-1
</verb></tscreen>
and reside in the font files
<tscreen><verb>
/usr/X11R6/lib/X11/fonts/Type1/UT*.pfa
</verb></tscreen>

Finally, X11R&relvers; also comes with Type&nbsp;1 versions of Bitstream
Courier and Charter.  These fonts have XLFD
<tscreen><verb>
-bitstream-courier-*-*-normal--0-0-0-0-m-0-iso8859-1
-bitstream-charter-*-*-normal--0-0-0-0-p-0-iso8859-1
</verb></tscreen>
and reside in the font files
<tscreen><verb>
/usr/X11R6/lib/X11/fonts/Type1/c*bt_.pfb
</verb></tscreen>

<sect1>The Bigelow &amp; Holmes Luxi family

<p>X11R&relvers; includes the <it/Luxi/ family of scalable fonts, in both
TrueType and Type&nbsp;1 format.  This family consists of the fonts
<it/Luxi Serif/, with XLFD
<tscreen><verb>
-b&amp;h-luxi serif-medium-*-normal--*-*-*-*-p-*-*-*
</verb></tscreen>
<it/Luxi Sans/, with XLFD
<tscreen><verb>
-b&amp;h-luxi sans-medium-*-normal--*-*-*-*-p-*-*-*
</verb></tscreen>
and <it/Luxi Mono/, with XLFD
<tscreen><verb>
-b&amp;h-luxi mono-medium-*-normal--*-*-*-*-m-*-*-*
</verb></tscreen>
Each of these fonts comes Roman, oblique, bold and bold oblique variants
The TrueType version have glyphs covering the basic ASCII Unicode
range, the Latin&nbsp;1 range, as well as the <it/Extended Latin/
range and some additional punctuation characters.  In particular,
these fonts include all the glyphs needed for ISO&nbsp;8859 parts 1,
2, 3, 4, 9, 13 and 15, as well as all the glyphs in the Adobe Standard
encoding and the Windows 3.1 character set.

The glyph coverage of the Type&nbsp;1 versions is somewhat reduced,
and only covers ISO&nbsp;8859 parts 1, 2 and 15 as well as the Adobe
Standard encoding.

The Luxi fonts are original designs by Kris Holmes and Charles 
Bigelow.  Luxi fonts include seriffed, sans serif, and monospaced 
styles, in roman and oblique, and normal and bold weights. The fonts 
share stem weight, x-height, capital height, ascent and descent, for 
graphical harmony.

The character width metrics of Luxi roman and bold fonts match those 
of core fonts bundled with popular operating and window systems.

The license terms for the Luxi fonts are included in the file
`<tt/COPYRIGHT.BH/', as well as in the <htmlurl
name="License document" url="LICENSE.html">.

Charles Bigelow and Kris Holmes from Bigelow and Holmes Inc. 
developed the Luxi typeface designs in Ikarus digital format.

URW++ Design and Development GmbH converted the Ikarus format fonts 
to TrueType and Type1 font programs and implemented the grid-fitting 
"hints" and kerning tables in the Luxi fonts.

For more information, please contact
<email>design@bigelowandholmes.com</email> or 
<email>info@urwpp.de</email>, or consult 
<url name="the URW++ web site" url="http://www.urwpp.de">.

An earlier version of the Luxi fonts was made available under the
name <em/Lucidux/.  This name should no longer be used due to trademark
uncertainties, and all traces of the <em/Lucidux/ name have been
removed from X11R&relvers;.

<sect>More about core fonts <label id="sec:more-core">

<p>This section describes X11R&relvers;-specific enhancements to the core
X11 fonts system.

<sect1>Core fonts and internationalisation <label id="sec:internationalisation">

<p>The scalable font backends (Type&nbsp;1 and TrueType) can
automatically re-encode fonts to the encoding specified in the
XLFD in `<tt/fonts.dir/'.  For example, a `<tt/fonts.dir/' file can
contain entries for the Type&nbsp;1 Courier font such as
<tscreen><verb>
cour.pfa -adobe-courier-medium-r-normal--0-0-0-0-m-0-iso8859-1 
cour.pfa -adobe-courier-medium-r-normal--0-0-0-0-m-0-iso8859-2
</verb></tscreen>
which will lead to the font being recoded to ISO&nbsp;8859-1 and
ISO&nbsp;8859-2 respectively.

<sect2>The <it/fontenc/ layer <label id="sec:fontenc">

<p>Two of the scalable backends (Type&nbsp;1 and the
<it/FreeType/ TrueType backend) use a common <it/fontenc/ layer for
font re-encoding.  This allows these backends to share their encoding
data, and allows simple configuration of new locales independently of
font type.

<it/Please note:/ the X-TrueType (X-TT) backend is not included
in X11R&relvers;.  That functionality has been merged into the FreeType
backend.>

In the <it/fontenc/ layer, an encoding is defined by a name (such as
<tt/iso8859-1/), possibly a number of aliases (alternate names), and
an ordered collection of mappings.  A mapping defines the way the
encoding can be mapped into one of the <it/target encodings/ known to
<it/fontenc/; currently, these consist of Unicode, Adobe glyph names,
and arbitrary TrueType ``cmap''s.

A number of encodings are hardwired into <it/fontenc/, and are
therefore always available; the hardcoded encodings cannot easily be
redefined.  These include:
<itemize>
<item> <tt/iso10646-1/: Unicode;
<item> <tt/iso8859-1/: ISO&nbsp;Latin-1 (Western Europe);
<item> <tt/iso8859-2/: ISO&nbsp;Latin-2 (Eastern Europe);
<item> <tt/iso8859-3/: ISO&nbsp;Latin-3 (Southern Europe);
<item> <tt/iso8859-4/: ISO&nbsp;Latin-4 (Northern Europe);
<item> <tt/iso8859-5/: ISO&nbsp;Cyrillic;
<item> <tt/iso8859-6/: ISO&nbsp;Arabic;
<item> <tt/iso8859-7/: ISO&nbsp;Greek;
<item> <tt/iso8859-8/: ISO&nbsp;Hebrew;
<item> <tt/iso8859-9/: ISO&nbsp;Latin-5 (Turkish);
<item> <tt/iso8859-10/: ISO&nbsp;Latin-6 (Nordic);
<item> <tt/iso8859-15/: ISO&nbsp;Latin-9, or Latin-0 (Revised
  Western-European);
<item> <tt/koi8-r/: KOI8 Russian;
<item> <tt/koi8-u/: KOI8 Ukrainian (see RFC 2319);
<item> <tt/koi8-ru/: KOI8 Russian/Ukrainian;
<item> <tt/koi8-uni/: KOI8 ``Unified'' (Russian, Ukrainian, and
  Byelorussian);
<item> <tt/koi8-e/: KOI8 ``European,'' ISO-IR-111, or ECMA-Cyrillic;
<item> <tt/microsoft-symbol/ and <tt/apple-roman/: these are only
  likely to be useful with TrueType symbol fonts.
</itemize>

Additional encodings can be added by defining <it/encoding files/.
When a font encoding is requested that the <it/fontenc/ layer doesn't
know about, the backend checks the directory in which the font file
resides (not necessarily the directory with <tt/fonts.dir/!) for a
file named `<tt/encodings.dir/'.  If found, this file is scanned for
the requested encoding, and the relevant encoding definition file is
read in.  The `<tt/mkfontdir/' utility, when invoked with the
`<tt/-e/' option followed by the name of a directory containing
encoding files, can be used to automatically build `<tt/encodings.dir/'
files.  Please see the <htmlurl name="mkfontdir(1)" url="mkfontdir.1.html">
manual page for more details.

A number of encoding files for common encodings are included with
X11R&relvers;.  Information on writing new encoding files can be found in
<ref id="sec:format-encoding-directory-files" name="Format of
encodings directory files"> and <ref id="sec:format-encoding-files"
name="Format of encoding files"> later in this document.

<sect2>Backend-specific notes about fontenc

<sect3>The <it/FreeType/ backend <label id="sec:fontenc-freetype"

<p>For TrueType and OpenType fonts, the FreeType backend scans the
mappings in order.  Mappings with a target of PostScript are ignored;
mappings with a TrueType or Unicode target are checked against all the
cmaps in the file.  The first applicable mapping is used.

For Type&nbsp;1 fonts, the FreeType backend first searches for a
mapping with a target of PostScript.  If one is found, it is used.
Otherwise, the backend searches for a mapping with target Unicode,
which is then composed with a built-in table mapping codes to glyph
names.  Note that this table only covers part of the Unicode code
points that have been assigned names by Adobe.

Specifying an encoding value of <tt/adobe-fontspecific/ for a
Type&nbsp;1 font disables the encoding mechanism.  This is useful with
symbol and incorrectly encoded fonts (see <ref
id="sec:incorrect-encoding" name="Incorrectly encoded fonts"> below).

If a suitable mapping is not found, the FreeType backend defaults to
ISO&nbsp;8859-1.

<sect3>Type&nbsp;1

<p>The Type&nbsp;1 backend behaves similarly to the FreeType backend
with Type&nbsp;1 fonts, except that it limits all encodings to 8-bit
codes.

<sect2>Format of encoding directory files <label id="sec:format-encoding-directory-files">

<p>In order to use a font in an encoding that the font backend does
not know about, you need to have an `<tt/encodings.dir/' file either
in the same directory as the font file used or in a system-wide
location (`<tt>/usr/X11R6/lib/X11/fonts/encodings/</tt>' by default).

The `<tt/encodings.dir/' file has a similar format to
`<tt/fonts.dir/'.  Its first line specifies the number of encodings,
while every successive line has two columns, the name of the encoding,
and the name of the encoding file; this can be relative to the current
directory, or absolute.  Every encoding name should agree with the
encoding name defined in the encoding file.  For example,

<tscreen><verb>
3
mulearabic-0 /usr/X11R6/lib/X11/fonts/encodings/mulearabic-0.enc
mulearabic-1 /usr/X11R6/lib/X11/fonts/encodings/mulearabic-1.enc
mulearabic-2 /usr/X11R6/lib/X11/fonts/encodings/mulearabic-2.enc
</verb></tscreen>

The name of an encoding <it/must/ be specified in the encoding file's
`<tt/STARTENCODING/' or `<tt/ALIAS/' line.  It is not enough to create
an `<tt/encodings.dir/' entry.

If your platform supports it (it probably does), encoding files may be
compressed or gzipped.

The `<tt/encoding.dir/' files are best maintained by the
`<tt/mkfontdir/' utility.  Please see the <htmlurl name="mkfontdir(1)"
url="mkfontdir.1.html"> manual page for more information.

<sect2>Format of encoding files <label id="sec:format-encoding-files">

<p>The encoding files are ``free form,'' <it/i.e./ any string of
whitespace is equivalent to a single space.  Keywords are parsed in a
non-case-sensitive manner, meaning that `<tt/size/', `<tt/SIZE/', and
`<tt/SiZE/' all parse as the same keyword; on the other hand, case is
significant in glyph names.

Numbers can be written in decimal, as in `<tt/256/', in hexadecimal,
as in `<tt/0x100/', or in octal, as in `<tt/0400/'.

Comments are introduced by a hash sign `<tt/#/'.  A `<tt/#/' may
appear at any point in a line, and all characters following the
`<tt/#/' are ignored, up to the end of the line.

The encoding file starts with the definition of the name of the
encoding, and possibly its alternate names (aliases):
<tscreen><verb>
STARTENCODING mulearabic-0
ALIAS arabic-0
</verb></tscreen>
The name of the encoding and its aliases should be suitable for use in
an XLFD font name, and therefore contain exactly one dash `<tt/-/'.

The encoding file may then optionally declare the size of the
encoding.  For a linear encoding (such as ISO&nbsp;8859-1), the SIZE
line specifies the maximum code plus one:
<tscreen><verb>
SIZE 0x2B
</verb></tscreen>
For a matrix encoding, it should specify two numbers.  The first is
the number of the last row plus one, the other, the highest column
number plus one.  In the case of `<tt/jisx0208.1990-0/'
(JIS&nbsp;X&nbsp;0208(1990), double-byte encoding, high bit clear), it
should be
<tscreen><verb>
SIZE 0x75 0x80
</verb></tscreen>
In the case of a matrix encoding, a `<tt/FIRSTINDEX/' line may be
included to specify the minimum glyph index in an encoding.  The
keyword `<tt/FIRSTINDEX/' is followed by two integers, the minimum row
number followed by the minimum column number:
<tscreen><verb>
FIRSTINDEX 0x20 0x20
</verb></tscreen>
In the case of a linear encoding, a `<tt/FIRSTINDEX/' line is not very
useful.  If for some reason however you chose to include on, it should
be followed by a single integer.

Note that in most font backends inclusion of a `<tt/FIRSTINDEX/' line
has the side effect of disabling default glyph generation, and this
keyword should therefore be avoided unless absolutely necessary.

Codes outside the region defined by the `<tt/SIZE/' and
`<tt/FIRSTINDEX/' lines are understood to be undefined.  Encodings
default to linear encoding with a size of 256 (0x100).  This means
that you must declare the size of all 16 bit encodings.

What follows is one or more mapping sections.  A mapping section
starts with a `<tt/STARTMAPPING/' line stating the target of the mapping.
The target may be one of:
<itemize>
<item>Unicode (ISO&nbsp;10646):
<tscreen><verb>
STARTMAPPING unicode
</verb></tscreen>
<item>a given TrueType ``cmap'':
<tscreen><verb>
STARTMAPPING cmap 3 1
</verb></tscreen>
<item>PostScript glyph names:
<tscreen><verb>
STARTMAPPING postscript
</verb></tscreen>
</itemize>
Every line in a mapping section maps one from the encoding being
defined to the target of the mapping.  In mappings with a Unicode or
TrueType mapping, codes are mapped to codes:
<tscreen><verb>
0x21 0x0660
0x22 0x0661
...
</verb></tscreen>
As an abbreviation, it is possible to map a contiguous range of codes
in a single line.  A line consisting of three integers
<tscreen><verb>
<it/start/ <it/end/ <it/target/
</verb></tscreen>
is an abbreviation for the range of lines
<tscreen>
<it/start/     <it/target/
</tscreen><tscreen>
<it/start/+1   <it/target/+1
</tscreen><tscreen>
...
</tscreen><tscreen>
<it/end/       <it/target/+<it/end/-<it/start/
</tscreen>
For example, the line
<tscreen><verb>
0x2121 0x215F 0x8140
</verb></tscreen>
is an abbreviation for
<tscreen><verb>
0x2121 0x8140
0x2122 0x8141
...
0x215F 0x817E
</verb></tscreen>
Codes not listed are assumed to map through the identity (<it/i.e./ to
the same numerical value).  In order to override this default mapping,
you may specify a range of codes to be undefined by using an
`<tt/UNDEFINE/' line:
<tscreen><verb>
UNDEFINE 0x00 0x2A
</verb></tscreen>
or, for a single code,
<tscreen><verb>
UNDEFINE 0x1234
</verb></tscreen>

PostScript mappings are different.  Every line in a PostScript mapping
maps a code to a glyph name
<tscreen><verb>
0x41 A
0x42 B
...
</verb></tscreen>
and codes not explicitly listed are undefined.

A mapping section ends with an <tt/ENDMAPPING/ line
<tscreen><verb>
ENDMAPPING
</verb></tscreen>
After all the mappings have been defined, the file ends with an
<tt/ENDENCODING/ line
<tscreen><verb>
ENDENCODING
</verb></tscreen>

In order to make future extensions to the format possible, lines
starting with an unknown keyword are silently ignored, as are mapping
sections with an unknown target.

<sect2>Using symbol fonts <label id="sec:symbol-fonts">

<p>Type&nbsp;1 symbol fonts should be installed using the
<tt/adobe-fontspecific/ encoding.

In an ideal world, all TrueType symbol fonts would be installed using
one of the <tt/microsoft-symbol/ and <tt/apple-roman/ encodings. A
number of symbol fonts, however, are not marked as such; such fonts
should be installed using <tt/microsoft-cp1252/, or, for older fonts,
<tt/microsoft-win3.1/.

In order to guarantee consistent results (especially between
Type&nbsp;1 and TrueType versions of the same font), it is possible to
define a special encoding for a given font. This has already been done
for the <tt/ZapfDingbats/ font; see the file
`<tt>encodings/adobe-dingbats.enc</tt>'.

<sect2>Hints about using badly encoded fonts <label id="sec:incorrect-encoding">

<p>A number of text fonts are incorrectly encoded. Incorrect encoding
is sometimes done by design, in order to make a font for an exotic
script appear like an ordinary Western text font on systems which are
not easily extended with new locale data.  It is often the result of
the font designer's laziness or incompetence; for some reason, most
people seem to find it easier to invent idiosyncratic glyph names
rather than follow the Adobe glyph list.

There are two ways of dealing with such fonts: using them with the
encoding they were designed for, and creating an <it/ad hoc/ encoding
file.

<sect3>Using fonts with the designer's encoding

<p>In the case of Type&nbsp;1 fonts, the font designer can specify a
default encoding; this encoding is requested by using the
`<tt/adobe-fontspecific/' encoding in the XLFD name. Sometimes, the
font designer omitted to specify a reasonable default encoding, in
which case you should experiment with `<tt/adobe-standard/',
`<tt/iso8859-1/', `<tt/microsoft-cp1252/', and
`<tt/microsoft-win3.1/'. (The encoding `<tt/microsoft-symbol/' doesn't
make sense for Type&nbsp;1 fonts).

TrueType fonts do not have a default encoding.  However, most TrueType
fonts are designed with either Microsoft or Apple platforms in mind,
so one of `<tt/microsoft-symbol/', `<tt/microsoft-cp1252/',
`<tt/microsoft-win3.1/', or `<tt/apple-roman/' should yield reasonable
results.

<sect3>Specifying an <it/ad hoc/ encoding file

<p>It is always possible to define an encoding file to put the glyphs
in a font in any desired order. Again, see the
`<tt>encodings/adobe-dingbats.enc</tt>' file to see how this is done.

<sect3>Specifying font aliases

<p>By following the directions above, you will find yourself with a
number of fonts with unusual names --- with encodings such as
`<tt/adobe-fontspecific/', `<tt/microsoft-win3.1/' <it/etc/.  In order
to use these fonts with standard applications, it may be useful to
remap them to their proper names.

This is done by writing a `<tt/fonts.alias/' file. The format of this file
is very simple: it consists of a series of lines each mapping an alias 
name to a font name.  A `<tt/fonts.alias/' file might look as follows:
<tscreen><verb>
"-ogonki-alamakota-medium-r-normal--0-0-0-0-p-0-iso8859-2" \
  "-ogonki-alamakota-medium-r-normal--0-0-0-0-p-0-adobe-fontspecific"
</verb></tscreen>
(both XLFD names on a single line).  The syntax of the
`<tt/fonts.alias/' file is more precisely described in the
<htmlurl name="mkfontdir(1)" url="mkfontdir.1.html"> manual page.

<sect1>Additional notes about scalable core fonts

<p>The FreeType (libfreetype-xtt2) backend (module `<tt/freetype/',
formerly known as <it/xfsft/) is able to deal with both TrueType and
Type&nbsp;1 fonts.  This puts it in conflict with the X-TT and Type&nbsp;1
backends respectively.

If both the FreeType and the Type&nbsp;1 backends are loaded, the
FreeType backend will be used for Type&nbsp;1 fonts.  If both the
FreeType and X-TT backends are loaded, X-TT will be used for TrueType
fonts.

<sect2>About the <it/FreeType/ backend

<p>The <it/FreeType/ (libfreetype-xtt2) backend (formerly <it/xfsft/)
is a backend based on version 2 of the FreeType library (see <url
url="http://www.freetype.org/" name="the FreeType web site">) and has
the X-TT functionalities for CJKV support provided by the After X-TT
Project (see <url url="http://x-tt.sourceforge.jp/" name="the After X-TT
Project web site">).  The <it/FreeType/ module has support for the
``fontenc'' style of internationalisation (see <ref id="sec:fontenc"
name="The fontenc layer">).  This backend supports TrueType font files
(`<tt/*.ttf/'), OpenType font files (`<tt/*.otf/'), TrueType Collections
(`<tt/*.ttc/'), OpenType Collections (`<tt/*.otc/') and Type 1 font
files (`<tt/*.pfa/' and `<tt/*.pfb/').

In order to access the faces in a TrueType Collection file, the face
number must be specified in the fonts.dir file before the filename,
within a pair of colons, or by setting the 'fn' TTCap option.  For example,

<tscreen><verb>
:1:mincho.ttc -misc-pmincho-medium-r-normal--0-0-0-0-p-0-jisx0208.1990-0
</verb></tscreen>

refers to face 1 in the `<tt/mincho.ttc/' TrueType Collection file.

The new <it/FreeType/ backend supports the extended
`<tt/fonts.dir/' syntax introduced by X-TrueType with a number
of options, collectively known as `TTCap'.  A `TTCap' entry follows the
general syntax

<tscreen><verb>
option=value:
</verb></tscreen>

and should be specified before the filename.  The new <it/FreeType/
almost perfectly supports TTCap options that are compatible with X-TT
1.4.  The Automatic Italic (`<tt/ai/'), Double Strike (`<tt/ds/') and
Bounding box Width (`<tt/bw/') options are indispensable in CJKV.
For example,

<tscreen><verb>
mincho.ttc -misc-mincho-medium-r-normal--0-0-0-0-c-0-jisx0208.1990-0
ds=y:mincho.ttc -misc-mincho-bold-r-normal--0-0-0-0-c-0-jisx0208.1990-0
ai=0.2:mincho.ttc -misc-mincho-medium-i-normal--0-0-0-0-c-0-jisx0208.1990-0
ds=y:ai=0.2:mincho.ttc -misc-mincho-bold-i-normal--0-0-0-0-c-0-jisx0208.1990-0
bw=0.5:mincho.ttc -misc-mincho-medium-r-normal--0-0-0-0-c-0-jisx0201.1976-0
bw=0.5:ds=y:mincho.ttc -misc-mincho-bold-r-normal--0-0-0-0-c-0-jisx0201.1976-0
bw=0.5:ai=0.2:mincho.ttc -misc-mincho-medium-i-normal--0-0-0-0-c-0-jisx0201.1976-0
bw=0.5:ds=y:ai=0.2:mincho.ttc -misc-mincho-bold-i-normal--0-0-0-0-c-0-jisx0201.1976-0
</verb></tscreen>

setup the complete combination of jisx0208 and jisx0201 using mincho.ttc
only.  More information on the TTCap syntax is found on <url
url="http://x-tt.sourceforge.jp/" name="the After X-TT Project page">.

The <it/FreeType/ backend uses the <it/fontenc/ layer in order to support
recoding of fonts; this was described in <ref id="sec:fontenc" name="The
fontenc layer"> and especially <ref id="sec:fontenc-freetype"
name="FreeType-specific notes about fontenc"> earlier in this document.

<sect2>About the <it/X-TrueType/ TrueType backend <label id="sec:X-TT">

<p>The `X-TrueType' backend is a backend based on version 1 of the FreeType
library.  X-TrueType doesn't use the `fontenc' layer for managing font
encodings, but instead uses its own database of encodings.

Since the functionalities for CJKV support introduced by X-TT have been
merged into the new <it/FreeType/ backend, the X-TT backend will be
removed from X11R&relvers;'s tree near the future.  Therefore, the use of
<it/FreeType/ backend is preferred over the X-TT backend.

General information on X-TrueType may be found at <url
url="http://x-tt.sourceforge.jp/" name="the After X-TT Project page">.

<sect2>Delayed glyph rasterisation

<p>When loading a proportional fonts which contain a huge number of glyphs,
the old <it/FreeType/ delayed glyph rasterisation until the time at which
the glyph was first used.   The new FreeType (libfreetype-xtt2) has an
improved `very lazy' metric calculation method to speed up the process when
loading TrueType or OpenType fonts.   Although the <it/X-TT/ module also
has this method, the "<tt/vl=y/" TTCap option must be set if you want to
use it.  This is the default method for <it/FreeType/ when it loads
multi-byte fonts.   Even if you use a unicode font which has tens of
thousands of glyphs, this delay will not be worrisome as long as you use
the new <it/FreeType/ backend -- its `very lazy' method is super-fast.

The maximum error of bitmap position using `very lazy' method is 1 pixel,
and is the same as that of a character-cell spacing.  When the X-TT
backend is used with the `<tt/vl=y/' option, a chipped bitmap is displayed
with certain fonts.  However, the new FreeType backend has minimal problem
with this, since it corrects left- and right-side bearings using
`italicAngle' in the TrueType/OpenType post table, and does automatic
correction of bitmap positions when rasterisation so that chipped bitmaps
are not displayed.  Nevertheless if you don't want to use the `very lazy'
method when using multi-bytes fonts, set `<tt/vl=n/' in the TTCap option to
disable it:

<tscreen><verb>
vl=n:luxirr.ttf -b&amp;h-Luxi Serif-medium-r-normal--0-0-0-0-p-0-iso10646-1
</verb></tscreen>

Of course, both backends also support an optimisation for character-cell
fonts (fonts with all glyph metrics equal, or terminal fonts).  A font
with an XLFD specifying a character-cell spacing `<tt/c/', as in

<tscreen><verb>
-misc-mincho-medium-r-normal--0-0-0-0-c-0-jisx0208.1990-0
</verb></tscreen>

or

<tscreen><verb>
fs=c:mincho.ttc -misc-mincho-medium-r-normal--0-0-0-0-p-0-jisx0208.1990-0
</verb></tscreen>

will not compute the metric for each glyph, but instead
trust the font to be a character-cell font.  You are
encouraged to make use of this optimisation when useful, but be warned
that not all monospaced fonts are character-cell fonts.

<sect>Appendix: background and terminology <label id="sec:background">
<sect1>Characters and glyphs

<p>A computer text-processing system inputs keystrokes and outputs
<it/glyphs/, small pictures that are assembled on paper or on a
computer screen.  Keystrokes and glyphs do not, in general, coincide:
for example, if the system does generate ligatures, then to the
sequence of two keystrokes &lt;<tt/f/&gt;&lt<tt/i/&gt; will typically
correspond a single glyph.  Similarly, if the system shapes Arabic
glyphs in a vaguely reasonable manner, then multiple different glyphs
may correspond to a single keystroke.

The complex transformation rules from keystrokes to glyphs are usually
factored into two simpler transformations, from keystrokes to
<it/characters/ and from characters to glyphs.  You may want to think
of characters as the basic unit of text that is stored <it/e.g./ in
the buffer of your text editor.  While the definition of a character
is intrinsically application-specific, a number of standardised
collections of characters have been defined.

A <it/coded character set/ is a set of characters together with a
mapping from integer codes --- known as <it/codepoints/ --- to
characters.  Examples of coded character sets include US-ASCII,
ISO&nbsp;8859-1, KOI8-R, and JIS&nbsp;X&nbsp;0208(1990).

A coded character set need not use 8 bit integers to index characters.
Many early systems used 6 bit character sets, while 16 bit (or more)
character sets are necessary for ideographic writing systems.

<sect1>Font files, fonts, and XLFD <label id="sec:xlfd">

<p>Traditionally, typographers speak about <it/typefaces/ and
<it/founts/.  A typeface is a particular style or design, such as
Times Italic, while a fount is a molten-lead incarnation of a given
typeface at a given size.

Digital fonts come in <it/font files/.  A font file contains the
information necessary for generating glyphs of a given typeface, and
applications using font files may access glyph information in an
arbitrary order.

Digital fonts may consist of bitmap data, in which case they are said
to be <it/bitmap fonts/.  They may also consist of a mathematical
description of glyph shapes, in which case they are said to be
<it/scalable fonts/.  Common formats for scalable font files are
<it/Type&nbsp;1/ (sometimes incorrectly called <it/ATM fonts/ or
<it/PostScript fonts/), <it/TrueType/ and <it/OpenType/.

The glyph data in a digital font needs to be indexed somehow.  How
this is done depends on the font file format.  In the case of
Type&nbsp;1 fonts, glyphs are identified by <it/glyph names/.  In the
case of TrueType fonts, glyphs are indexed by integers corresponding
to one of a number of indexing schemes (usually Unicode --- see below).

The X11 core fonts system uses the data in a font file to generate
<it/font instances/, which are collections of glyphs at a given size
indexed according to a given encoding.

X11 core font instances are usually specified using a notation known
as the <it/X Logical Font Description/ (XLFD).  An XLFD starts with a
dash `<tt/-/', and consists of fourteen fields separated by dashes,
for example:
<tscreen><verb>
-adobe-courier-medium-r-normal--12-120-75-75-m-70-iso8859-1
</verb></tscreen>
Or particular interest are the last two fields `<tt/iso8859-1/', which
specify the font instance's encoding.

A scalable font is specified by an XLFD which contains zeroes instead
of some fields:
<tscreen><verb>
-adobe-courier-medium-r-normal--0-0-0-0-m-0-iso8859-1
</verb></tscreen>

X11 font instances may also be specified by short name.  Unlike an
XLFD, a short name has no structure and is simply a conventional name
for a font instance.  Two short names are of particular interest, as
the server will not start if font instances with these names cannot be
opened.  These are `<tt/fixed/', which specifies the fallback font to
use when the requested font cannot be opened, and `<tt/cursor/', which
specifies the set of glyphs to be used by the mouse pointer.

Short names are usually implemented as aliases to XLFDs; the
standard `<tt/fixed/' and `<tt/cursor/' aliases are defined in
<tscreen><verb>
/usr/X11R6/lib/X11/font/misc/fonts.alias
</verb></tscreen>

<sect1>Unicode

<p>Unicode (<url url="http://www.unicode.org">) is a coded character
set with the goal of uniquely identifying all characters for all
scripts, current and historical.  While Unicode was explicitly not
designed as a glyph encoding scheme, it is often possible to use it as
such.

Unicode is an <it/open/ character set, meaning that codepoint
assignments may be added to Unicode at any time (once specified,
though, an assignment can never be changed).  For this reason, a
Unicode font will be <it/sparse/, meaning that it only defines glyphs
for a subset of the character registry of Unicode.

The Unicode standard is defined in parallel with the international
standard ISO&nbsp;10646.  Assignments in the two standards are always
equivalent, and we often use the terms <it/Unicode/ and
<it/ISO&nbsp;10646/ interchangeably.

When used in the X11 core fonts system, Unicode-encoded fonts should
have the last two fields of their XLFD set to `<tt/iso10646-1/'.

<sect>References

<p>X11R&relvers; comes with extensive documentation in the form of manual
pages and typeset documents.  Before installing fonts, you really should
read the <htmlurl name="fontconfig(3)" url="fontconfig.3.html"> and
<htmlurl name="mkfontdir(1)" url="mkfontdir.1.html"> manual pages; other
manual pages of interest include <htmlurl name="X(7)" url="X.7.html">,
<htmlurl name="Xserver(1)" url="Xserver.1.html">, <htmlurl name="xset(1)"
url="xset.1.html">, <htmlurl name="Xft(3)" url="Xft.3.html">, <htmlurl
name="xlsfonts(1)" url="xlsfonts.1.html"> and <htmlurl name="showfont(1)"
url="showfont.1.html">.  In addition, you may want to read the X Logical
Font Description document, by Jim Flowers, which is provided in the file
`<tt>xc/doc/xlfd.PS.Z</tt>'.

The latest released version of the X11R&relvers; documentation (including
this document and all manual pages) can be found from
<url name="current X11R&relvers; documentation"
     url="http://wiki.x.org/">.

The <url name="comp.fonts FAQ"
         url="http://www.faqs.org/faqs/by-newsgroup/comp/comp.fonts.html">, 
which is unfortunately no longer being maintained, contains a wealth
of information about digital fonts.

Xft and Fontconfig are described on
<url name="Keith Packard's Fontconfig site"
     url="http://www.fontconfig.org">.

The 
<url name="xfsft home page"
     url="http://www.dcs.ed.ac.uk/home/jec/programs/xfsft/">
has been superseded by this document, and is now obsolete; you may
however still find some of the information that it contains useful.
<url name="Joerg Pommnitz' xfsft page"
     url="http://www.joerg-pommnitz.de/TrueType/xfsft.html"> 
is the canonical source for the `<tt/ttmkfdir/' utility, which is the
ancestor of <tt/mkfontscale/.

<url name="The author's software pages"
     url="http://www.pps.jussieu.fr/~jch/software/">
might or might not contain related scribbles and development versions
of software.

The documentation of <it/X-TrueType/ is available from <url
url="http://x-tt.sourceforge.jp/" name="the After X-TT Project page">.

A number of East-Asian CIDFonts are available from 
<url name="O'Reilly's FTP site"
     url="ftp://ftp.oreilly.com/pub/examples/nutshell/cjkv/adobe/">. 

While the <url url="http://www.unicode.org" name="Unicode consortium site">
may be of interest,  you are more likely to find what you need in
Markus Kuhn's <url url="http://www.cl.cam.ac.uk/~mgk25/unicode.html"
name="UTF-8 and Unicode FAQ">.

The IANA RFC documents, available from a number of sites throughout
the world, often provide interesting information about character set
issues; see for example RFC&nbsp;373.

</article>
<!-- Who was it who designed Linuxdoc, and was he drunk at the time? -->
