diff options
| author | Alan Coopersmith <alan.coopersmith@oracle.com> | 2010-11-01 18:59:25 -0700 |
|---|---|---|
| committer | Alan Coopersmith <alan.coopersmith@oracle.com> | 2010-11-02 19:33:52 -0700 |
| commit | 922bb8b668ef64514b906f8ab07bc6b81f35b75c (patch) | |
| tree | ed0aaa497726b35e63c66613a630596b6c097c67 | |
| parent | b12e1b22c0ecb7009ce31aa34206a277aff12faf (diff) | |
Convert font docs from DocBook SGML to DocBook XML
Uses newer tools for formatting, better matching other new docs
Moved from sgml/fonts to new directory general/fonts
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
| -rw-r--r-- | configure.ac | 2 | ||||
| -rw-r--r-- | general/Makefile.am | 2 | ||||
| -rw-r--r-- | general/fonts/Makefile.am | 8 | ||||
| -rw-r--r-- | general/fonts/fonts.xml (renamed from sgml/fonts/fonts.sgml) | 1996 | ||||
| -rw-r--r-- | sgml/Makefile.am | 2 | ||||
| -rw-r--r-- | sgml/fonts/Makefile.am | 5 |
6 files changed, 1007 insertions, 1008 deletions
diff --git a/configure.ac b/configure.ac index d16954d..29de701 100644 --- a/configure.ac +++ b/configure.ac @@ -46,11 +46,11 @@ XORG_CHECK_DOCBOOK AC_CONFIG_FILES([Makefile general/Makefile + general/fonts/Makefile general/input/Makefile general/graphics/Makefile man/Makefile sgml/Makefile - sgml/fonts/Makefile sgml/platforms/Makefile specs/Makefile specs/CTEXT/Makefile diff --git a/general/Makefile.am b/general/Makefile.am index 3e282b3..919fd03 100644 --- a/general/Makefile.am +++ b/general/Makefile.am @@ -1,6 +1,6 @@ # Process this file with automake to create Makefile.in -SUBDIRS = input graphics +SUBDIRS = fonts input graphics doc_sources = ReleaseNotes.xml diff --git a/general/fonts/Makefile.am b/general/fonts/Makefile.am new file mode 100644 index 0000000..8c98b66 --- /dev/null +++ b/general/fonts/Makefile.am @@ -0,0 +1,8 @@ +# Process this file with automake to create Makefile.in + +doc_sources = fonts.xml + +xmldir = $(docdir)/fonts +dist_xml_DATA = $(doc_sources) + +include $(top_srcdir)/xmlrules.in diff --git a/sgml/fonts/fonts.sgml b/general/fonts/fonts.xml index 0d82c63..72c0723 100644 --- a/sgml/fonts/fonts.sgml +++ b/general/fonts/fonts.xml @@ -1,53 +1,56 @@ -<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.2//EN" [ -<!ENTITY % defs SYSTEM "X11/defs.ent"> %defs; +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" + "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" +[ +<!ENTITY % defs SYSTEM "/xorg-sgml-doctools/X11/defs.ent"> %defs; ]> -<Article> +<article> <articleinfo> -<Title>Fonts in X11R&relvers;</Title> -<AUTHOR><firstname>Juliusz</firstname><surname>Chroboczek</surname> -<EMAIL>jch@freedesktop.org</EMAIL> -</AUTHOR> -<PubDate>23 October 2009</PubDate> +<title>Fonts in X11R&relvers;</title> +<author><firstname>Juliusz</firstname><surname>Chroboczek</surname> +<email>jch@freedesktop.org</email> +</author> +<pubdate>23 October 2009</pubdate> </articleinfo> -<Sect1> -<Title>Introduction</Title> +<sect1> +<title>Introduction</title> -<Para> +<para> This document describes the support for fonts in X11R&relvers;. -<XRef LinkEnd="sec-installing"> is aimed at the +<xref linkend="sec-installing"/> 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. -</Para> +</para> -<Para> +<para> We assume some familiarity with digital fonts. If anything is not -clear to you, please consult <XRef LinkEnd="sec-background"> at the end of this document for background -information. -</Para> +clear to you, please consult <xref linkend="sec-background" /> at the +end of this document for background information. +</para> -<Sect2> -<Title>Two font systems</Title> +<sect2> +<title>Two font systems</title> -<Para> +<para> X11 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 yet be distributed with implementations of X11 that are not based on either XFree86 or X11R6.8 or later. -</Para> +</para> -<Para> +<para> 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. -</Para> +</para> -<Para> +<para> Xft was designed from the start to provide good support for scalable fonts, and to do so efficiently. Unlike the core fonts system, it supports features such as anti-aliasing and sub-pixel rasterisation. @@ -55,126 +58,126 @@ 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. -</Para> +</para> -<Para> +<para> Xft is not compatible with the core fonts system: usage of Xft requires 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. -</Para> +</para> -</Sect2> +</sect2> -</Sect1> +</sect1> -<Sect1 id="sec-installing" xreflabel="Installing fonts"> -<Title>Installing fonts</Title> +<sect1 id="sec-installing" xreflabel="Installing fonts"> +<title>Installing fonts</title> -<Para> +<para> This section explains how to configure both Xft and the core fonts system to access newly-installed fonts. -</Para> +</para> -<Sect2 id="sec-configuring-xft"> -<Title>Configuring Xft</Title> +<sect2 id="sec-configuring-xft"> +<title>Configuring Xft</title> -<Para> +<para> Xft has no configuration mechanism itself, it relies upon the -<ULink URL="http://www.fontconfig.org/">fontconfig</ULink> +<ulink url="http://www.fontconfig.org/">fontconfig</ulink> library to configure and customise fonts. That library is not specific to the X Window system, and does not rely on any particular font output mechanism. -</Para> +</para> -<Sect3> -<Title>Installing fonts in Xft</Title> +<sect3> +<title>Installing fonts in Xft</title> -<Para> +<para> Fontconfig looks for fonts in a set of well-known directories that include all of X11R&relvers;'s standard font directories -(`<Literal remap="tt">/usr/share/fonts/X11/*</Literal>') by default) as well as a -directory called `<Literal remap="tt">.fonts/</Literal>' in the user's home directory. +(`<filename>/usr/share/fonts/X11/*</filename>') by default) as well as a +directory called `<filename>.fonts/</filename>' 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. -<Screen> +<screen> $ cp lucbr.ttf ~/.fonts/ -</Screen> +</screen> 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, you may run the command `<Literal remap="tt">fc-cache</Literal>'. +line, you may run the command `<command>fc-cache</command>'. -<Screen> +<screen> $ fc-cache -</Screen> +</screen> -</Para> +</para> -<Para> +<para> In order to globally update the system-wide Fontconfig information on Unix systems, you will typically need to run this command as root: -<Screen> +<screen> $ su -c fc-cache -</Screen> +</screen> -</Para> +</para> -</Sect3> +</sect3> -<Sect3> -<Title>Fine-tuning Xft</Title> +<sect3> +<title>Fine-tuning Xft</title> -<Para> +<para> Fontconfig's behaviour is controlled by a set of configuration -files: a standard configuration file, `<Literal remap="tt">/etc/fonts/fonts.conf</Literal>', -a host-specific configuration file, `<Literal remap="tt">/etc/fonts/local.conf</Literal>', -and a user-specific file called `<Literal remap="tt">.fonts.conf</Literal>' in the user's +files: a standard configuration file, `<filename>/etc/fonts/fonts.conf</filename>', +a host-specific configuration file, `<filename>/etc/fonts/local.conf</filename>', +and a user-specific file called `<filename>.fonts.conf</filename>' in the user's home directory (this can be overridden with the -`<Literal remap="tt">FONTCONFIG_FILE</Literal>' environment variable). -</Para> +`<envar>FONTCONFIG_FILE</envar>' environment variable). +</para> -<Para> +<para> Every Fontconfig configuration file must start with the following boilerplate: -<Screen> +<screen> <?xml version="1.0"?> <!DOCTYPE fontconfig SYSTEM "fonts.dtd"> <fontconfig> -</Screen> +</screen> In addition, every Fontconfig configuration file must end with the following line: -<Screen> +<screen> </fontconfig> -</Screen> +</screen> -</Para> +</para> -<Para> +<para> The default Fontconfig configuration file includes the directory -`<Literal remap="tt">˜/.fonts/</Literal>' in the list of directories searched for font +`<filename>˜/.fonts/</filename>' 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: -<Screen> +<screen> <dir>/usr/local/share/fonts/</dir> -</Screen> +</screen> -</Para> +</para> -<Para> +<para> Another useful option is the ability to disable anti-aliasing (font smoothing) for selected fonts. This can be done with the following syntax: -<Screen> +<screen> <match target="font"> <test qual="any" name="family"> <string>Lucida Console</string> @@ -183,1245 +186,1238 @@ syntax: <bool>false</bool> </edit> </match> -</Screen> +</screen> Anti-aliasing can be disabled for all fonts by the following incantation: -<Screen> +<screen> <match target="font"> <edit name="antialias" mode="assign"> <bool>false</bool> </edit> </match> -</Screen> +</screen> -</Para> +</para> -<Para> +<para> 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 -<Screen> +<screen> $ xdpyinfo -ext RENDER | grep sub-pixel -</Screen> +</screen> 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: -<Screen> +<screen> <match target="font"> <edit name="rgba" mode="assign"> <const>rgb</const> </edit> </match> -</Screen> +</screen> -The string `<Literal remap="tt">rgb</Literal>' within the -`<Literal remap="tt"><const></Literal>'...`<Literal remap="tt"></const></Literal>' +The string `<literal remap="tt">rgb</literal>' within the +`<literal remap="tt"><const></literal>'...`<literal remap="tt"></const></literal>' specifies the order of pixel components on your display, and should be -changed to match your hardware; it can be one of `<Literal remap="tt">rgb</Literal> (normal -LCD screen), `<Literal remap="tt">bgr</Literal>' (backwards LCD screen), `<Literal remap="tt">vrgb</Literal>' (LCD -screen rotated clockwise) or `<Literal remap="tt">vbgr</Literal>' (LCD screen rotated +changed to match your hardware; it can be one of `<literal remap="tt">rgb</literal> (normal +LCD screen), `<literal remap="tt">bgr</literal>' (backwards LCD screen), `<literal remap="tt">vrgb</literal>' (LCD +screen rotated clockwise) or `<literal remap="tt">vbgr</literal>' (LCD screen rotated counterclockwise). -</Para> +</para> -</Sect3> +</sect3> -<Sect3> -<Title>Configuring applications</Title> +<sect3> +<title>Configuring applications</title> -<Para> +<para> A growing number of applications use Xft in preference to the core fonts system. Some applications, however, need to be explicitly configured to use Xft. -</Para> +</para> -<Para> +<para> A case in point is XTerm, which can be set to use Xft by using the -`<Literal remap="tt">-fa</Literal>' command line option or by setting the `<Literal remap="tt">XTerm*faceName</Literal>' +`<literal remap="tt">-fa</literal>' command line option or by setting the `<literal remap="tt">XTerm*faceName</literal>' resource: -<Screen> +<screen> XTerm*faceName: Courier -</Screen> +</screen> or -<Screen> +<screen> $ xterm -fa "Courier" -</Screen> +</screen> -</Para> +</para> -<Para> +<para> 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. -</Para> +</para> -<Para> +<para> Gnome applications and Mozilla Firefox will use Xft by default. -</Para> +</para> -</Sect3> +</sect3> -</Sect2> +</sect2> -<Sect2> -<Title>Configuring the core X11 fonts system</Title> +<sect2> +<title>Configuring the core X11 fonts system</title> -<Para> +<para> Installing fonts in the core system is a two step process. First, -you need to create a <Emphasis remap="it">font directory</Emphasis> that contains all the +you need to create a <emphasis remap="it">font directory</emphasis> 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 <Emphasis remap="it">font path</Emphasis>. -</Para> +including it in the <emphasis remap="it">font path</emphasis>. +</para> -<Sect3> -<Title>Installing bitmap fonts</Title> +<sect3> +<title>Installing bitmap fonts</title> -<Para> +<para> 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.) -</Para> +</para> -<Para> +<para> 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 `<Literal remap="tt">bdftopcf</Literal>', <Emphasis remap="it">e.g.</Emphasis> +command `<command>bdftopcf</command>', <emphasis remap="it">e.g.</emphasis> -<Screen> +<screen> $ bdftopcf courier12.bdf -</Screen> +</screen> You will then want to compress the resulting PCF font files: -<Screen> +<screen> $ gzip courier12.pcf -</Screen> +</screen> -</Para> +</para> -<Para> +<para> After the fonts have been converted, you should copy all the font files that you wish to make available into a arbitrary directory, say -`<Literal remap="tt">/usr/local/share/fonts/bitmap/</Literal>'. You should then create the -index file `<Literal remap="tt">fonts.dir</Literal>' by running the command `<Literal remap="tt">mkfontdir</Literal>' -(please see the <ULink -URL="mkfontdir.1.html" ->mkfontdir(1)</ULink +`<filename>/usr/local/share/fonts/bitmap/</filename>'. You should then create the +index file `<filename>fonts.dir</filename>' by running the command `<command>mkfontdir</command>' +(please see the <ulink +url="mkfontdir.1.html" +>mkfontdir(1)</ulink > manual page for more information): -<Screen> +<screen> $ mkdir /usr/local/share/fonts/bitmap/ $ cp *.pcf.gz /usr/local/share/fonts/bitmap/ $ mkfontdir /usr/local/share/fonts/bitmap/ -</Screen> +</screen> -</Para> +</para> -<Para> +<para> All that remains is to tell the X server about the existence of the -new font directory; see <XRef LinkEnd="sec-set-font-path"> below. -</Para> +new font directory; see <xref linkend="sec-set-font-path"/> below. +</para> -</Sect3> +</sect3> -<Sect3> -<Title>Installing scalable fonts</Title> +<sect3> +<title>Installing scalable fonts</title> -<Para> +<para> The X11R&relvers; server supports scalable fonts in multiple formats, including Type 1, TrueType, and OpenType/CFF. (Earlier versions of X11 also included support for the Speedo and CID scalable font formats, but that is not included in current releases.) -</Para> +</para> -<Para> +<para> Installing scalable fonts is very similar to installing bitmap fonts: -you create a directory with the font files, and run `<Literal remap="tt">mkfontdir</Literal>' -to create an index file called `<Literal remap="tt">fonts.dir</Literal>'. -</Para> +you create a directory with the font files, and run `<command>mkfontdir</command>' +to create an index file called `<filename>fonts.dir</filename>'. +</para> -<Para> -There is, however, a big difference: `<Literal remap="tt">mkfontdir</Literal>' cannot +<para> +There is, however, a big difference: `<command>mkfontdir</command>' cannot automatically recognise scalable font files. For that reason, you must first index all the font files in a file called -`<Literal remap="tt">fonts.scale</Literal>'. While this can be done by hand, it is best done -by using the `<Literal remap="tt">mkfontscale</Literal>' utility. +`<filename>fonts.scale</filename>'. While this can be done by hand, it is best done +by using the `<command>mkfontscale</command>' utility. -<Screen> +<screen> $ mkfontscale /usr/local/share/fonts/Type1/ $ mkfontdir /usr/local/share/fonts/Type1/ -</Screen> +</screen> Under some circumstances, it may be necessary to modify the -`<Literal remap="tt">fonts.scale</Literal>' file generated by <Literal remap="tt">mkfontscale</Literal>; for more -information, please see the <ULink -URL="mkfontdir.1.html" ->mkfontdir(1)</ULink -> and <ULink -URL="mkfontscale.1.html" ->mkfontscale(1)</ULink -> manual pages and <XRef LinkEnd="sec-internationalisation"> +`<filename>fonts.scale</filename>' file generated by <command>mkfontscale</command>; for more +information, please see the <ulink +url="mkfontdir.1.html" +>mkfontdir(1)</ulink +> and <ulink +url="mkfontscale.1.html" +>mkfontscale(1)</ulink +> manual pages and <xref linkend="sec-internationalisation"/> later in this document. -</Para> +</para> -</Sect3> +</sect3> -<Sect3 id="sec-cid-fonts" xreflabel="Installing CIDFonts"> -<Title>CID-keyed fonts </Title> +<sect3 id="sec-cid-fonts" xreflabel="Installing CIDFonts"> +<title>CID-keyed fonts </title> -<Para> +<para> The CID-keyed font format was designed by Adobe Systems for fonts with large character sets. The CID-keyed format is obsolete, as it has been superseded by other formats such as OpenType/CFF and support for CID-keyed fonts has been removed from X11. -</Para> +</para> -</Sect3> +</sect3> -<Sect3 id="sec-set-font-path" xreflabel="Setting the server font path"> -<Title>Setting the server's font path </Title> +<sect3 id="sec-set-font-path" xreflabel="Setting the server font path"> +<title>Setting the server's font path </title> -<Para> +<para> The list of directories where the server looks for fonts is known -as the <Emphasis remap="it">font path</Emphasis>. Informing the server of the existence of a new +as the <emphasis remap="it">font path</emphasis>. Informing the server of the existence of a new font directory consists of putting it on the font path. -</Para> +</para> -<Para> +<para> 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. -</Para> +</para> -<Para> +<para> 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 `<Literal remap="tt">:unscaled</Literal>' +bitmap fonts when a scalable font can be used. (The `<literal remap="tt">:unscaled</literal>' hack, while still supported, should no longer be necessary in X11R&relvers;.) -</Para> +</para> -<Para> +<para> You may check the font path of the running server by typing the command -<Screen> +<screen> $ xset q -</Screen> +</screen> -</Para> +</para> -<Sect4> -<Title>Font path catalogue directories</Title> +<sect4> +<title>Font path catalogue directories</title> -<Para> +<para> You can specify a special kind of font path directory in the form -<Literal remap="tt">catalogue:<dir></Literal>. -The directory specified after the <Literal remap="tt">catalogue:</Literal> +<filename>catalogue:<dir></filename>. +The directory specified after the <filename>catalogue:</filename> prefix will be scanned for symlinks and each symlink destination will be added as a local font path entry. -</Para> +</para> -<Para> +<para> The symlink can be suffixed by attributes such as -'<Literal remap="tt">unscaled</Literal>', which will be passed through +'<literal remap="tt">unscaled</literal>', which will be passed through to the underlying font path entry. The only exception is the newly -introduced '<Literal remap="tt">pri</Literal>' attribute, which will be +introduced '<literal remap="tt">pri</literal>' attribute, which will be used for ordering the font paths specified by the symlinks. -</Para> +</para> -<Para> +<para> An example configuration: -<Screen> +<screen> 75dpi:unscaled:pri=20 -> /usr/share/X11/fonts/75dpi ghostscript:pri=60 -> /usr/share/fonts/default/ghostscript misc:unscaled:pri=10 -> /usr/share/X11/fonts/misc type1:pri=40 -> /usr/share/X11/fonts/Type1 type1:pri=50 -> /usr/share/fonts/default/Type1 -</Screen> -</Para> +</screen> +</para> -<Para> -This will add <Literal remap="tt">/usr/share/X11/fonts/misc</Literal> as the +<para> +This will add <filename>/usr/share/X11/fonts/misc</filename> as the first font path entry with the attribute -<Literal remap="tt">unscaled</Literal>. This is functionally equivalent to +<literal remap="tt">unscaled</literal>. This is functionally equivalent to setting the following font path: -<Screen> +<screen> /usr/share/X11/fonts/misc:unscaled, /usr/share/X11/fonts/75dpi:unscaled, /usr/share/X11/fonts/Type1, /usr/share/fonts/default/Type1, /usr/share/fonts/default/ghostscript -</Screen> -</Para> -</Sect4> +</screen> +</para> +</sect4> -<Sect4> -<Title>Temporary modification of the font path</Title> +<sect4> +<title>Temporary modification of the font path</title> -<Para> -The `<Literal remap="tt">xset</Literal>' utility may be used to modify the font path for the -current session. The font path is set with the command <Literal remap="tt">xset fp</Literal>; -a new element is added to the front with <Literal remap="tt">xset +fp</Literal>, and added to -the end with <Literal remap="tt">xset fp+</Literal>. For example, +<para> +The `<command>xset</command>' utility may be used to modify the font path for the +current session. The font path is set with the command <command>xset fp</command>; +a new element is added to the front with <command>xset +fp</command>, and added to +the end with <command>xset fp+</command>. For example, -<Screen> +<screen> $ xset +fp /usr/local/fonts/Type1 $ xset fp+ /usr/local/fonts/bitmap -</Screen> +</screen> -</Para> +</para> -<Para> +<para> Conversely, an element may be removed from the front of the font path -with `<Literal remap="tt">xset -fp</Literal>', and removed from the end with `<Literal remap="tt">xset fp-</Literal>'. +with `<command>xset -fp</command>', and removed from the end with `<command>xset fp-</command>'. You may reset the font path to its default value with -`<Literal remap="tt">xset fp default</Literal>'. -</Para> +`<command>xset fp default</command>'. +</para> -<Para> -For more information, please consult the <ULink -URL="xset.1.html" ->xset(1)</ULink +<para> +For more information, please consult the <ulink +url="xset.1.html" +>xset(1)</ulink > manual page. -</Para> +</para> -</Sect4> +</sect4> -<Sect4> -<Title>Permanent modification of the font path</Title> +<sect4> +<title>Permanent modification of the font path</title> -<Para> +<para> The default font path (the one used just after server startup or -after `<Literal remap="tt">xset fp default</Literal>') may be specified in the +after `<command>xset fp default</command>') may be specified in the X server's -`<Literal remap="tt">xorg.conf</Literal>' file. It is computed by appending all the -directories mentioned in the `<Literal remap="tt">FontPath</Literal>' entries of the -`<Literal remap="tt">Files</Literal>' section in the order in which they appear. If no font path is specified in a config file, the server uses a default +`<filename>xorg.conf</filename>' file. It is computed by appending all the +directories mentioned in the `<literal remap="tt">FontPath</literal>' entries of the +`<literal remap="tt">Files</literal>' section in the order in which they appear. If no font path is specified in a config file, the server uses a default value specified when it was built. -<Screen> +<screen> FontPath "/usr/local/fonts/Type1" ... FontPath "/usr/local/fonts/bitmap" -</Screen> +</screen> -</Para> +</para> -<Para> -For more information, please consult the <ULink -URL="xorg.conf.5.html" ->xorg.conf(5)</ULink +<para> +For more information, please consult the <ulink +url="xorg.conf.5.html" +>xorg.conf(5)</ulink > manual page. -</Para> +</para> -</Sect4> +</sect4> -</Sect3> +</sect3> -<Sect3 id="sec-troubleshooting-core"> -<Title>Troubleshooting </Title> +<sect3 id="sec-troubleshooting-core"> +<title>Troubleshooting </title> -<Para> +<para> If you seem to be unable to use some of the fonts you have -installed, the first thing to check is that the `<Literal remap="tt">fonts.dir</Literal>' files +installed, the first thing to check is that the `<filename>fonts.dir</filename>' 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. -</Para> +</para> -<Para> +<para> X11R&relvers; supports the BDF, PCF, SNF, Type 1, TrueType, and OpenType font formats. However, not all X11R&relvers; servers come with all the font backends configured in. -</Para> +</para> -<Para> +<para> On most platforms, the X11R&relvers; servers no longer uses font backends from modules that are loaded at runtime. The built in font support corresponds to the functionality formerly provided by these modules: - <ItemizedList> - <ListItem> + <itemizedlist> + <listitem> - <Para> - <Literal remap="tt">"bitmap"</Literal>: - bitmap fonts (`<Literal remap="tt">*.bdf</Literal>', - `<Literal remap="tt">*.pcf</Literal>' - and `<Literal remap="tt">*.snf</Literal>'); - </Para> - </ListItem> - <ListItem> + <para> + <literal remap="tt">"bitmap"</literal>: + bitmap fonts (`<filename>*.bdf</filename>', + `<filename>*.pcf</filename>' + and `<filename>*.snf</filename>'); + </para> + </listitem> + <listitem> - <Para> - <Literal remap="tt">"freetype"</Literal>: - TrueType fonts (`<Literal remap="tt">*.ttf</Literal>' and - `<Literal remap="tt">*.ttc</Literal>'), - OpenType fonts (`<Literal remap="tt">*.otf</Literal>' and - `<Literal remap="tt">*.otc</Literal>') and - Type 1 fonts (`<Literal remap="tt">*.pfa</Literal>' - and `<Literal remap="tt">*.pfb</Literal>'). - </Para> - </ListItem> + <para> + <literal remap="tt">"freetype"</literal>: + TrueType fonts (`<filename>*.ttf</filename>' and + `<filename>*.ttc</filename>'), + OpenType fonts (`<filename>*.otf</filename>' and + `<filename>*.otc</filename>') and + Type 1 fonts (`<filename>*.pfa</filename>' + and `<filename>*.pfb</filename>'). + </para> + </listitem> - </ItemizedList> + </itemizedlist> -</Para> +</para> -</Sect3> +</sect3> -</Sect2> +</sect2> -</Sect1> +</sect1> -<Sect1> -<Title>Fonts included with X11R&relvers;</Title> +<sect1> +<title>Fonts included with X11R&relvers;</title> -<Sect2> -<Title>Standard bitmap fonts</Title> +<sect2> +<title>Standard bitmap fonts</title> -<Para> +<para> The Sample Implementation of X11 (SI) comes with a large number of -bitmap fonts, including the `<Literal remap="tt">fixed</Literal>' family, and bitmap versions +bitmap fonts, including the `<literal remap="tt">fixed</literal>' family, and bitmap versions of Courier, Times, Helvetica and some members of the Lucida family. -</Para> +</para> -<Para> +<para> In X11R&relvers;, a number of these fonts are provided in Unicode-encoded font files now. 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. -</Para> +</para> -<Para> +<para> For example, the font file -<Screen> +<screen> /usr/share/fonts/X11/misc/6x13.bdf -</Screen> +</screen> with XLFD -<Screen> +<screen> -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso10646-1 -</Screen> +</screen> -is a Unicode-encoded version of the standard `<Literal remap="tt">fixed</Literal>' font with +is a Unicode-encoded version of the standard `<literal remap="tt">fixed</literal>' 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 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. -</Para> +</para> -<Para> +<para> This font is used at build time for generating the font files -<Screen> +<screen> 6x13-ISO8859-1.bdf 6x13-ISO8859-2.bdf ... 6x13-ISO8859-15.bdf 6x13-KOI8-R.bdf -</Screen> +</screen> with respective XLFDs -<Screen> +<screen> -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 -</Screen> +</screen> -The standard short name `<Literal remap="tt">fixed</Literal>' is normally an alias for +The standard short name `<literal remap="tt">fixed</literal>' is normally an alias for -<Screen> +<screen> -misc-fixed-medium-r-normal--13-120-75-75-c-60-iso8859-1 -</Screen> +</screen> -</Para> +</para> -</Sect2> +</sect2> -<Sect2> -<Title>The ClearlyU Unicode font family</Title> +<sect2> +<title>The ClearlyU Unicode font family</title> -<Para> +<para> The ClearlyU family of fonts provides a set of 12 pt, 100 dpi proportional fonts with many of the glyphs needed for Unicode text. Together, the fonts contain approximately 7500 glyphs. -</Para> +</para> -<Para> +<para> The main ClearlyU font has the XLFD -<Screen> +<screen> -mutt-clearlyu-medium-r-normal--17-120-100-100-p-101-iso10646-1 -</Screen> +</screen> and resides in the font file -<Screen> +<screen> /usr/share/fonts/X11/misc/cu12.pcf.gz -</Screen> +</screen> Additional ClearlyU fonts include -<Screen> +<screen> -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 -</Screen> +</screen> -</Para> +</para> -<Para> -The <Emphasis remap="it">Alternate Glyphs</Emphasis> font contains additional glyph shapes that +<para> +The <emphasis remap="it">Alternate Glyphs</emphasis> 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 (<Emphasis remap="it">e.g.</Emphasis> the Urdu heh). -</Para> +commonly used alternate shape (<emphasis remap="it">e.g.</emphasis> the Urdu heh). +</para> -<Para> -The <Emphasis remap="it">PUA</Emphasis> font contains extra glyphs that are useful for certain +<para> +The <emphasis remap="it">PUA</emphasis> font contains extra glyphs that are useful for certain rendering purposes. -</Para> +</para> -<Para> -The <Emphasis remap="it">Arabic Extra</Emphasis> font contains the glyphs necessary for +<para> +The <emphasis remap="it">Arabic Extra</emphasis> font contains the glyphs necessary for characters that don't have all of their possible shapes encoded in ISO 10646. The glyphs are roughly ordered according to the order of the characters in the ISO 10646 standard. -</Para> +</para> -<Para> -The <Emphasis remap="it">Ligature</Emphasis> font contains ligatures for various scripts that +<para> +The <emphasis remap="it">Ligature</emphasis> font contains ligatures for various scripts that may be useful for improved presentation of text. -</Para> +</para> -</Sect2> +</sect2> -<Sect2> -<Title>Standard scalable fonts</Title> +<sect2> +<title>Standard scalable fonts</title> -<Para> +<para> X11R&relvers; includes all the scalable fonts distributed with X11R6. -</Para> +</para> -<Sect3> -<Title>Standard Type 1 fonts</Title> +<sect3> +<title>Standard Type 1 fonts</title> -<Para> +<para> The IBM Courier set of fonts cover ISO 8859-1 and ISO 8859-2 as well as Adobe Standard Encoding. These fonts have XLFD -<Screen> +<screen> -adobe-courier-medium-*-*--0-0-0-0-m-0-*-* -</Screen> +</screen> and reside in the font files -<Screen> +<screen> /usr/share/fonts/X11/Type1/cour*.pfa -</Screen> +</screen> -</Para> +</para> -<Para> +<para> The Adobe Utopia set of fonts only cover ISO 8859-1 as well as Adobe Standard Encoding. These fonts have XLFD -<Screen> +<screen> -adobe-utopia-*-*-normal--0-0-0-0-p-0-iso8859-1 -</Screen> +</screen> and reside in the font files -<Screen> +<screen> /usr/share/fonts/X11/Type1/UT*.pfa -</Screen> +</screen> -</Para> +</para> -<Para> +<para> Finally, X11R&relvers; also comes with Type 1 versions of Bitstream Courier and Charter. These fonts have XLFD -<Screen> +<screen> -bitstream-courier-*-*-normal--0-0-0-0-m-0-iso8859-1 -bitstream-charter-*-*-normal--0-0-0-0-p-0-iso8859-1 -</Screen> +</screen> and reside in the font files -<Screen> +<screen> /usr/share/fonts/X11/Type1/c*bt_.pfb -</Screen> +</screen> -</Para> +</para> -</Sect3> +</sect3> -</Sect2> +</sect2> -<Sect2> -<Title>The Bigelow & Holmes Luxi family</Title> +<sect2> +<title>The Bigelow & Holmes Luxi family</title> -<Para> -X11R&relvers; includes the <Emphasis remap="it">Luxi</Emphasis> family of scalable fonts, in both +<para> +X11R&relvers; includes the <emphasis remap="it">Luxi</emphasis> family of scalable fonts, in both TrueType and Type 1 format. This family consists of the fonts -<Emphasis remap="it">Luxi Serif</Emphasis>, with XLFD +<emphasis remap="it">Luxi Serif</emphasis>, with XLFD -<Screen> +<screen> -b&h-luxi serif-medium-*-normal--*-*-*-*-p-*-*-* -</Screen> +</screen> -<Emphasis remap="it">Luxi Sans</Emphasis>, with XLFD +<emphasis remap="it">Luxi Sans</emphasis>, with XLFD -<Screen> +<screen> -b&h-luxi sans-medium-*-normal--*-*-*-*-p-*-*-* -</Screen> +</screen> -and <Emphasis remap="it">Luxi Mono</Emphasis>, with XLFD +and <emphasis remap="it">Luxi Mono</emphasis>, with XLFD -<Screen> +<screen> -b&h-luxi mono-medium-*-normal--*-*-*-*-m-*-*-* -</Screen> +</screen> 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 1 range, as well as the <Emphasis remap="it">Extended Latin</Emphasis> +range, the Latin 1 range, as well as the <emphasis remap="it">Extended Latin</emphasis> range and some additional punctuation characters. In particular, these fonts include all the glyphs needed for ISO 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. -</Para> +</para> -<Para> +<para> The glyph coverage of the Type 1 versions is somewhat reduced, and only covers ISO 8859 parts 1, 2 and 15 as well as the Adobe Standard encoding. -</Para> +</para> -<Para> +<para> 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. -</Para> +</para> -<Para> +<para> The character width metrics of Luxi roman and bold fonts match those of core fonts bundled with popular operating and window systems. -</Para> +</para> -<Para> +<para> The license terms for the Luxi fonts are included in the file -`<Literal remap="tt">COPYRIGHT.BH</Literal>', as well as in the <ULink -URL="../LICENSE.html">License document</ULink>. -</Para> +`<filename>COPYRIGHT.BH</filename>', as well as in the <ulink +url="../LICENSE.html">License document</ulink>. +</para> -<Para> +<para> Charles Bigelow and Kris Holmes from Bigelow and Holmes Inc. developed the Luxi typeface designs in Ikarus digital format. -</Para> +</para> -<Para> +<para> 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. -</Para> +</para> -<Para> +<para> For more information, please contact -<EMAIL ->design@bigelowandholmes.com</EMAIL -> or -<EMAIL ->info@urwpp.de</EMAIL ->, or consult -<ULink -URL="http://www.urwpp.de" ->the URW++ web site</ULink ->. -</Para> +<email>design@bigelowandholmes.com</email> or +<email>info@urwpp.de</email>, or consult +<ulink url="http://www.urwpp.de">the URW++ web site</ulink>. +</para> -<Para> +<para> An earlier version of the Luxi fonts was made available under the -name <Emphasis>Lucidux</Emphasis>. This name should no longer be used due to trademark -uncertainties, and all traces of the <Emphasis>Lucidux</Emphasis> name have been -removed from X11R&relvers;. -</Para> +name <emphasis>Lucidux</emphasis>. This name should no longer be used due to +trademark uncertainties, and all traces of the <emphasis>Lucidux</emphasis> +name have been removed from X11R&relvers;. +</para> -</Sect2> +</sect2> -</Sect1> +</sect1> -<Sect1 id="sec-more-core"> -<Title>More about core fonts </Title> +<sect1 id="sec-more-core"> +<title>More about core fonts </title> -<Para> +<para> This section describes X11R&relvers;-specific enhancements to the core X11 fonts system. -</Para> +</para> -<Sect2 id="sec-internationalisation" xreflabel="Core fonts and +<sect2 id="sec-internationalisation" xreflabel="Core fonts and internationalisation"> -<Title>Core fonts and internationalisation </Title> +<title>Core fonts and internationalisation </title> -<Para> +<para> The scalable font backends (Type 1 and TrueType) can automatically re-encode fonts to the encoding specified in the -XLFD in `<Literal remap="tt">fonts.dir</Literal>'. For example, a `<Literal remap="tt">fonts.dir</Literal>' file can +XLFD in `<filename>fonts.dir</filename>'. For example, a `<filename>fonts.dir</filename>' file can contain entries for the Type 1 Courier font such as -<Screen> +<screen> 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 -</Screen> +</screen> which will lead to the font being recoded to ISO 8859-1 and ISO 8859-2 respectively. -</Para> +</para> -<Sect3 id="sec-fontenc"> -<Title>The <Emphasis remap="it">fontenc</Emphasis> layer </Title> +<sect3 id="sec-fontenc"> +<title>The <emphasis remap="it">fontenc</emphasis> layer </title> -<Para> +<para> Two of the scalable backends (Type 1 and the -<Emphasis remap="it">FreeType</Emphasis> TrueType backend) use a common <Emphasis remap="it">fontenc</Emphasis> layer for +<emphasis remap="it">FreeType</emphasis> TrueType backend) use a common <emphasis remap="it">fontenc</emphasis> 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. -</Para> +</para> -<Para> -<Emphasis remap="it">Please note:</Emphasis> the X-TrueType (X-TT) backend is not included +<para> +<emphasis remap="it">Please note:</emphasis> the X-TrueType (X-TT) backend is not included in X11R&relvers;. That functionality has been merged into the FreeType backend.> -</Para> +</para> -<Para> -In the <Emphasis remap="it">fontenc</Emphasis> layer, an encoding is defined by a name (such as -<Literal remap="tt">iso8859-1</Literal>), possibly a number of aliases (alternate names), and +<para> +In the <emphasis remap="it">fontenc</emphasis> layer, an encoding is defined by a name (such as +<literal remap="tt">iso8859-1</literal>), 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 <Emphasis remap="it">target encodings</Emphasis> known to -<Emphasis remap="it">fontenc</Emphasis>; currently, these consist of Unicode, Adobe glyph names, +encoding can be mapped into one of the <emphasis remap="it">target encodings</emphasis> known to +<emphasis remap="it">fontenc</emphasis>; currently, these consist of Unicode, Adobe glyph names, and arbitrary TrueType ``cmap''s. -</Para> +</para> -<Para> -A number of encodings are hardwired into <Emphasis remap="it">fontenc</Emphasis>, and are +<para> +A number of encodings are hardwired into <emphasis remap="it">fontenc</emphasis>, and are therefore always available; the hardcoded encodings cannot easily be redefined. These include: -<ItemizedList> -<ListItem> - -<Para> - <Literal remap="tt">iso10646-1</Literal>: Unicode; -</Para> -</ListItem> -<ListItem> - -<Para> - <Literal remap="tt">iso8859-1</Literal>: ISO Latin-1 (Western Europe); -</Para> -</ListItem> -<ListItem> - -<Para> - <Literal remap="tt">iso8859-2</Literal>: ISO Latin-2 (Eastern Europe); -</Para> -</ListItem> -<ListItem> - -<Para> - <Literal remap="tt">iso8859-3</Literal>: ISO Latin-3 (Southern Europe); -</Para> -</ListItem> -<ListItem> - -<Para> - <Literal remap="tt">iso8859-4</Literal>: ISO Latin-4 (Northern Europe); -</Para> -</ListItem> -<ListItem> - -<Para> - <Literal remap="tt">iso8859-5</Literal>: ISO Cyrillic; -</Para> -</ListItem> -<ListItem> - -<Para> - <Literal remap="tt">iso8859-6</Literal>: ISO Arabic; -</Para> -</ListItem> -<ListItem> - -<Para> - <Literal remap="tt">iso8859-7</Literal>: ISO Greek; -</Para> -</ListItem> -<ListItem> - -<Para> - <Literal remap="tt">iso8859-8</Literal>: ISO Hebrew; -</Para> -</ListItem> -<ListItem> - -<Para> - <Literal remap="tt">iso8859-9</Literal>: ISO Latin-5 (Turkish); -</Para> -</ListItem> -<ListItem> - -<Para> - <Literal remap="tt">iso8859-10</Literal>: ISO Latin-6 (Nordic); -</Para> -</ListItem> -<ListItem> - -<Para> - <Literal remap="tt">iso8859-15</Literal>: ISO Latin-9, or Latin-0 (Revised +<itemizedlist> +<listitem> + +<para> + <literal remap="tt">iso10646-1</literal>: Unicode; +</para> +</listitem> +<listitem> + +<para> + <literal remap="tt">iso8859-1</literal>: ISO Latin-1 (Western Europe); +</para> +</listitem> +<listitem> + +<para> + <literal remap="tt">iso8859-2</literal>: ISO Latin-2 (Eastern Europe); +</para> +</listitem> +<listitem> + +<para> + <literal remap="tt">iso8859-3</literal>: ISO Latin-3 (Southern Europe); +</para> +</listitem> +<listitem> + +<para> + <literal remap="tt">iso8859-4</literal>: ISO Latin-4 (Northern Europe); +</para> +</listitem> +<listitem> + +<para> + <literal remap="tt">iso8859-5</literal>: ISO Cyrillic; +</para> +</listitem> +<listitem> + +<para> + <literal remap="tt">iso8859-6</literal>: ISO Arabic; +</para> +</listitem> +<listitem> + +<para> + <literal remap="tt">iso8859-7</literal>: ISO Greek; +</para> +</listitem> +<listitem> + +<para> + <literal remap="tt">iso8859-8</literal>: ISO Hebrew; +</para> +</listitem> +<listitem> + +<para> + <literal remap="tt">iso8859-9</literal>: ISO Latin-5 (Turkish); +</para> +</listitem> +<listitem> + +<para> + <literal remap="tt">iso8859-10</literal>: ISO Latin-6 (Nordic); +</para> +</listitem> +<listitem> + +<para> + <literal remap="tt">iso8859-15</literal>: ISO Latin-9, or Latin-0 (Revised Western-European); -</Para> -</ListItem> -<ListItem> - -<Para> - <Literal remap="tt">koi8-r</Literal>: KOI8 Russian; -</Para> -</ListItem> -<ListItem> - -<Para> - <Literal remap="tt">koi8-u</Literal>: KOI8 Ukrainian (see RFC 2319); -</Para> -</ListItem> -<ListItem> - -<Para> - <Literal remap="tt">koi8-ru</Literal>: KOI8 Russian/Ukrainian; -</Para> -</ListItem> -<ListItem> - -<Para> - <Literal remap="tt">koi8-uni</Literal>: KOI8 ``Unified'' (Russian, Ukrainian, and +</para> +</listitem> +<listitem> + +<para> + <literal remap="tt">koi8-r</literal>: KOI8 Russian; +</para> +</listitem> +<listitem> + +<para> + <literal remap="tt">koi8-u</literal>: KOI8 Ukrainian (see RFC 2319); +</para> +</listitem> +<listitem> + +<para> + <literal remap="tt">koi8-ru</literal>: KOI8 Russian/Ukrainian; +</para> +</listitem> +<listitem> + +<para> + <literal remap="tt">koi8-uni</literal>: KOI8 ``Unified'' (Russian, Ukrainian, and Byelorussian); -</Para> -</ListItem> -<ListItem> - -<Para> - <Literal remap="tt">koi8-e</Literal>: KOI8 ``European,'' ISO-IR-111, or ECMA-Cyrillic; -</Para> -</ListItem> -<ListItem> - -<Para> - <Literal remap="tt">microsoft-symbol</Literal> and <Literal remap="tt">apple-roman</Literal>: these are only +</para> +</listitem> +<listitem> + +<para> + <literal remap="tt">koi8-e</literal>: KOI8 ``European,'' ISO-IR-111, or ECMA-Cyrillic; +</para> +</listitem> +<listitem> + +<para> + <literal remap="tt">microsoft-symbol</literal> and <literal remap="tt">apple-roman</literal>: these are only likely to be useful with TrueType symbol fonts. -</Para> -</ListItem> +</para> +</listitem> -</ItemizedList> +</itemizedlist> -</Para> +</para> -<Para> -Additional encodings can be added by defining <Emphasis remap="it">encoding files</Emphasis>. -When a font encoding is requested that the <Emphasis remap="it">fontenc</Emphasis> layer doesn't +<para> +Additional encodings can be added by defining <emphasis remap="it">encoding files</emphasis>. +When a font encoding is requested that the <emphasis remap="it">fontenc</emphasis> layer doesn't know about, the backend checks the directory in which the font file -resides (not necessarily the directory with <Literal remap="tt">fonts.dir</Literal>!) for a -file named `<Literal remap="tt">encodings.dir</Literal>'. If found, this file is scanned for +resides (not necessarily the directory with <filename>fonts.dir</filename>!) for a +file named `<filename>encodings.dir</filename>'. If found, this file is scanned for the requested encoding, and the relevant encoding definition file is -read in. The `<Literal remap="tt">mkfontdir</Literal>' utility, when invoked with the -`<Literal remap="tt">-e</Literal>' option followed by the name of a directory containing -encoding files, can be used to automatically build `<Literal remap="tt">encodings.dir</Literal>' -files. Please see the <ULink -URL="mkfontdir.1.html" ->mkfontdir(1)</ULink +read in. The `<command>mkfontdir</command>' utility, when invoked with the +`<literal remap="tt">-e</literal>' option followed by the name of a directory containing +encoding files, can be used to automatically build `<filename>encodings.dir</filename>' +files. Please see the <ulink +url="mkfontdir.1.html" +>mkfontdir(1)</ulink > manual page for more details. -</Para> +</para> -<Para> +<para> A number of encoding files for common encodings are included with X11R&relvers;. Information on writing new encoding files can be found in -<XRef LinkEnd="sec-format-encoding-directory-files"> and <XRef LinkEnd="sec-format-encoding-files"> later in this document. -</Para> +<xref linkend="sec-format-encoding-directory-files"/> and <xref linkend="sec-format-encoding-files"/> later in this document. +</para> -</Sect3> +</sect3> -<Sect3> -<Title>Backend-specific notes about fontenc</Title> +<sect3> +<title>Backend-specific notes about fontenc</title> -<Sect4 id="sec-fontenc-freetype"> -<Title>The <Emphasis remap="it">FreeType</Emphasis> backend </Title> +<sect4 id="sec-fontenc-freetype"> +<title>The <emphasis remap="it">FreeType</emphasis> backend </title> -<Para> +<para> 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. -</Para> +</para> -<Para> +<para> For Type 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. -</Para> +</para> -<Para> -Specifying an encoding value of <Literal remap="tt">adobe-fontspecific</Literal> for a +<para> +Specifying an encoding value of <literal remap="tt">adobe-fontspecific</literal> for a Type 1 font disables the encoding mechanism. This is useful with -symbol and incorrectly encoded fonts (see <XRef LinkEnd="sec-incorrect-encoding"> below). -</Para> +symbol and incorrectly encoded fonts (see <xref linkend="sec-incorrect-encoding"/> below). +</para> -<Para> +<para> If a suitable mapping is not found, the FreeType backend defaults to ISO 8859-1. -</Para> +</para> -</Sect4> +</sect4> -</Sect3> +</sect3> -<Sect3 id="sec-format-encoding-directory-files" xreflabel="Format of +<sect3 id="sec-format-encoding-directory-files" xreflabel="Format of encodings directory files"> -<Title>Format of encoding directory files </Title> +<title>Format of encoding directory files </title> -<Para> +<para> In order to use a font in an encoding that the font backend does -not know about, you need to have an `<Literal remap="tt">encodings.dir</Literal>' file either +not know about, you need to have an `<filename>encodings.dir</filename>' file either in the same directory as the font file used or in a system-wide -location (`<Literal remap="tt">/usr/share/fonts/X11/encodings/</Literal>' by default). -</Para> +location (`<filename>/usr/share/fonts/X11/encodings/</filename>' by default). +</para> -<Para> -The `<Literal remap="tt">encodings.dir</Literal>' file has a similar format to -`<Literal remap="tt">fonts.dir</Literal>'. Its first line specifies the number of encodings, +<para> +The `<filename>encodings.dir</filename>' file has a similar format to +`<filename>fonts.dir</filename>'. 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, -</Para> +</para> -<Para> +<para> -<Screen> +<screen> 3 mulearabic-0 /usr/share/fonts/X11/encodings/mulearabic-0.enc mulearabic-1 /usr/share/fonts/X11/encodings/mulearabic-1.enc mulearabic-2 /usr/share/fonts/X11/encodings/mulearabic-2.enc -</Screen> +</screen> -</Para> +</para> -<Para> -The name of an encoding <Emphasis remap="it">must</Emphasis> be specified in the encoding file's -`<Literal remap="tt">STARTENCODING</Literal>' or `<Literal remap="tt">ALIAS</Literal>' line. It is not enough to create -an `<Literal remap="tt">encodings.dir</Literal>' entry. -</Para> +<para> +The name of an encoding <emphasis remap="it">must</emphasis> be specified in the encoding file's +`<literal remap="tt">STARTENCODING</literal>' or `<literal remap="tt">ALIAS</literal>' line. It is not enough to create +an `<filename>encodings.dir</filename>' entry. +</para> -<Para> +<para> If your platform supports it (it probably does), encoding files may be compressed or gzipped. -</Para> +</para> -<Para> -The `<Literal remap="tt">encoding.dir</Literal>' files are best maintained by the -`<Literal remap="tt">mkfontdir</Literal>' utility. Please see the <ULink -URL="mkfontdir.1.html" ->mkfontdir(1)</ULink +<para> +The `<filename>encoding.dir</filename>' files are best maintained by the +`<command>mkfontdir</command>' utility. Please see the <ulink +url="mkfontdir.1.html" +>mkfontdir(1)</ulink > manual page for more information. -</Para> +</para> -</Sect3> +</sect3> -<Sect3 id="sec-format-encoding-files" xreflabel="Format of encoding files"> -<Title>Format of encoding files </Title> +<sect3 id="sec-format-encoding-files" xreflabel="Format of encoding files"> +<title>Format of encoding files </title> -<Para> -The encoding files are ``free form,'' <Emphasis remap="it">i.e.</Emphasis> any string of +<para> +The encoding files are ``free form,'' <emphasis remap="it">i.e.</emphasis> any string of whitespace is equivalent to a single space. Keywords are parsed in a -non-case-sensitive manner, meaning that `<Literal remap="tt">size</Literal>', `<Literal remap="tt">SIZE</Literal>', and -`<Literal remap="tt">SiZE</Literal>' all parse as the same keyword; on the other hand, case is +non-case-sensitive manner, meaning that `<literal remap="tt">size</literal>', `<literal remap="tt">SIZE</literal>', and +`<literal remap="tt">SiZE</literal>' all parse as the same keyword; on the other hand, case is significant in glyph names. -</Para> +</para> -<Para> -Numbers can be written in decimal, as in `<Literal remap="tt">256</Literal>', in hexadecimal, -as in `<Literal remap="tt">0x100</Literal>', or in octal, as in `<Literal remap="tt">0400</Literal>'. -</Para> +<para> +Numbers can be written in decimal, as in `<literal remap="tt">256</literal>', in hexadecimal, +as in `<literal remap="tt">0x100</literal>', or in octal, as in `<literal remap="tt">0400</literal>'. +</para> -<Para> -Comments are introduced by a hash sign `<Literal remap="tt">#</Literal>'. A `<Literal remap="tt">#</Literal>' may +<para> +Comments are introduced by a hash sign `<literal remap="tt">#</literal>'. A `<literal remap="tt">#</literal>' may appear at any point in a line, and all characters following the -`<Literal remap="tt">#</Literal>' are ignored, up to the end of the line. -</Para> +`<literal remap="tt">#</literal>' are ignored, up to the end of the line. +</para> -<Para> +<para> The encoding file starts with the definition of the name of the encoding, and possibly its alternate names (aliases): -<Screen> +<screen> STARTENCODING mulearabic-0 ALIAS arabic-0 -</Screen> +</screen> The name of the encoding and its aliases should be suitable for use in -an XLFD font name, and therefore contain exactly one dash `<Literal remap="tt">-</Literal>'. -</Para> +an XLFD font name, and therefore contain exactly one dash `<literal remap="tt">-</literal>'. +</para> -<Para> +<para> The encoding file may then optionally declare the size of the encoding. For a linear encoding (such as ISO 8859-1), the SIZE line specifies the maximum code plus one: -<Screen> +<screen> SIZE 0x2B -</Screen> +</screen> 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 `<Literal remap="tt">jisx0208.1990-0</Literal>' +number plus one. In the case of `<literal remap="tt">jisx0208.1990-0</literal>' (JIS X 0208(1990), double-byte encoding, high bit clear), it should be -<Screen> +<screen> SIZE 0x75 0x80 -</Screen> +</screen> -In the case of a matrix encoding, a `<Literal remap="tt">FIRSTINDEX</Literal>' line may be +In the case of a matrix encoding, a `<literal remap="tt">FIRSTINDEX</literal>' line may be included to specify the minimum glyph index in an encoding. The -keyword `<Literal remap="tt">FIRSTINDEX</Literal>' is followed by two integers, the minimum row +keyword `<literal remap="tt">FIRSTINDEX</literal>' is followed by two integers, the minimum row number followed by the minimum column number: -<Screen> +<screen> FIRSTINDEX 0x20 0x20 -</Screen> +</screen> -In the case of a linear encoding, a `<Literal remap="tt">FIRSTINDEX</Literal>' line is not very +In the case of a linear encoding, a `<literal remap="tt">FIRSTINDEX</literal>' line is not very useful. If for some reason however you chose to include on, it should be followed by a single integer. -</Para> +</para> -<Para> -Note that in most font backends inclusion of a `<Literal remap="tt">FIRSTINDEX</Literal>' line +<para> +Note that in most font backends inclusion of a `<literal remap="tt">FIRSTINDEX</literal>' line has the side effect of disabling default glyph generation, and this keyword should therefore be avoided unless absolutely necessary. -</Para> +</para> -<Para> -Codes outside the region defined by the `<Literal remap="tt">SIZE</Literal>' and -`<Literal remap="tt">FIRSTINDEX</Literal>' lines are understood to be undefined. Encodings +<para> +Codes outside the region defined by the `<literal remap="tt">SIZE</literal>' and +`<literal remap="tt">FIRSTINDEX</literal>' 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. -</Para> +</para> -<Para> +<para> What follows is one or more mapping sections. A mapping section -starts with a `<Literal remap="tt">STARTMAPPING</Literal>' line stating the target of the mapping. +starts with a `<literal remap="tt">STARTMAPPING</literal>' line stating the target of the mapping. The target may be one of: -<ItemizedList> -<ListItem> +<itemizedlist> +<listitem> -<Para> +<para> Unicode (ISO 10646): -<Screen> +<screen> STARTMAPPING unicode -</Screen> +</screen> -</Para> -</ListItem> -<ListItem> +</para> +</listitem> +<listitem> -<Para> +<para> a given TrueType ``cmap'': -<Screen> +<screen> STARTMAPPING cmap 3 1 -</Screen> +</screen> -</Para> -</ListItem> -<ListItem> +</para> +</listitem> +<listitem> -<Para> +<para> PostScript glyph names: -<Screen> +<screen> STARTMAPPING postscript -</Screen> +</screen> -</Para> -</ListItem> +</para> +</listitem> -</ItemizedList> +</itemizedlist> 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: -<Screen> +<screen> 0x21 0x0660 0x22 0x0661 ... -</Screen> +</screen> As an abbreviation, it is possible to map a contiguous range of codes in a single line. A line consisting of three integers -<Screen> +<screen> <it/start/ <it/end/ <it/target/ -</Screen> +</screen> is an abbreviation for the range of lines -<Screen> -<Emphasis remap="it">start</Emphasis> <Emphasis remap="it">target</Emphasis> -</Screen> +<screen> +<emphasis remap="it">start</emphasis> <emphasis remap="it">target</emphasis> +</screen> -<Screen> -<Emphasis remap="it">start</Emphasis>+1 <Emphasis remap="it">target</Emphasis>+1 -</Screen> +<screen> +<emphasis remap="it">start</emphasis>+1 <emphasis remap="it">target</emphasis>+1 +</screen> -<Screen> +<screen> ... -</Screen> +</screen> -<Screen> -<Emphasis remap="it">end</Emphasis> <Emphasis remap="it">target</Emphasis>+<Emphasis remap="it">end</Emphasis>-<Emphasis remap="it">start</Emphasis> -</Screen> +<screen> +<emphasis remap="it">end</emphasis> <emphasis remap="it">target</emphasis>+<emphasis remap="it">end</emphasis>-<emphasis remap="it">start</emphasis> +</screen> For example, the line -<Screen> +<screen> 0x2121 0x215F 0x8140 -</Screen> +</screen> is an abbreviation for -<Screen> +<screen> 0x2121 0x8140 0x2122 0x8141 ... 0x215F 0x817E -</Screen> +</screen> -Codes not listed are assumed to map through the identity (<Emphasis remap="it">i.e.</Emphasis> to +Codes not listed are assumed to map through the identity (<emphasis remap="it">i.e.</emphasis> 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 -`<Literal remap="tt">UNDEFINE</Literal>' line: +`<literal remap="tt">UNDEFINE</literal>' line: -<Screen> +<screen> UNDEFINE 0x00 0x2A -</Screen> +</screen> or, for a single code, -<Screen> +<screen> UNDEFINE 0x1234 -</Screen> +</screen> -</Para> +</para> -<Para> +<para> PostScript mappings are different. Every line in a PostScript mapping maps a code to a glyph name -<Screen> +<screen> 0x41 A 0x42 B ... -</Screen> +</screen> and codes not explicitly listed are undefined. -</Para> +</para> -<Para> -A mapping section ends with an <Literal remap="tt">ENDMAPPING</Literal> line +<para> +A mapping section ends with an <literal remap="tt">ENDMAPPING</literal> line -<Screen> +<screen> ENDMAPPING -</Screen> +</screen> After all the mappings have been defined, the file ends with an -<Literal remap="tt">ENDENCODING</Literal> line +<literal remap="tt">ENDENCODING</literal> line -<Screen> +<screen> ENDENCODING -</Screen> +</screen> -</Para> +</para> -<Para> +<para> 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. -</Para> +</para> -</Sect3> +</sect3> -<Sect3 id="sec-symbol-fonts"> -<Title>Using symbol fonts </Title> +<sect3 id="sec-symbol-fonts"> +<title>Using symbol fonts </title> -<Para> +<para> Type 1 symbol fonts should be installed using the -<Literal remap="tt">adobe-fontspecific</Literal> encoding. -</Para> +<literal remap="tt">adobe-fontspecific</literal> encoding. +</para> -<Para> +<para> In an ideal world, all TrueType symbol fonts would be installed using -one of the <Literal remap="tt">microsoft-symbol</Literal> and <Literal remap="tt">apple-roman</Literal> encodings. A +one of the <literal remap="tt">microsoft-symbol</literal> and <literal remap="tt">apple-roman</literal> encodings. A number of symbol fonts, however, are not marked as such; such fonts -should be installed using <Literal remap="tt">microsoft-cp1252</Literal>, or, for older fonts, -<Literal remap="tt">microsoft-win3.1</Literal>. -</Para> +should be installed using <literal remap="tt">microsoft-cp1252</literal>, or, for older fonts, +<literal remap="tt">microsoft-win3.1</literal>. +</para> -<Para> +<para> In order to guarantee consistent results (especially between Type 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 <Literal remap="tt">ZapfDingbats</Literal> font; see the file -`<Literal remap="tt">encodings/adobe-dingbats.enc</Literal>'. -</Para> +for the <literal remap="tt">ZapfDingbats</literal> font; see the file +`<filename>encodings/adobe-dingbats.enc</filename>'. +</para> -</Sect3> +</sect3> -<Sect3 id="sec-incorrect-encoding" xreflabel="Incorrectly encoded fonts"> -<Title>Hints about using badly encoded fonts </Title> +<sect3 id="sec-incorrect-encoding" xreflabel="Incorrectly encoded fonts"> +<title>Hints about using badly encoded fonts </title> -<Para> +<para> 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 @@ -1429,152 +1425,152 @@ 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. -</Para> +</para> -<Para> +<para> There are two ways of dealing with such fonts: using them with the -encoding they were designed for, and creating an <Emphasis remap="it">ad hoc</Emphasis> encoding +encoding they were designed for, and creating an <emphasis remap="it">ad hoc</emphasis> encoding file. -</Para> +</para> -<Sect4> -<Title>Using fonts with the designer's encoding</Title> +<sect4> +<title>Using fonts with the designer's encoding</title> -<Para> +<para> In the case of Type 1 fonts, the font designer can specify a default encoding; this encoding is requested by using the -`<Literal remap="tt">adobe-fontspecific</Literal>' encoding in the XLFD name. Sometimes, the +`<literal remap="tt">adobe-fontspecific</literal>' encoding in the XLFD name. Sometimes, the font designer omitted to specify a reasonable default encoding, in -which case you should experiment with `<Literal remap="tt">adobe-standard</Literal>', -`<Literal remap="tt">iso8859-1</Literal>', `<Literal remap="tt">microsoft-cp1252</Literal>', and -`<Literal remap="tt">microsoft-win3.1</Literal>'. (The encoding `<Literal remap="tt">microsoft-symbol</Literal>' doesn't +which case you should experiment with `<literal remap="tt">adobe-standard</literal>', +`<literal remap="tt">iso8859-1</literal>', `<literal remap="tt">microsoft-cp1252</literal>', and +`<literal remap="tt">microsoft-win3.1</literal>'. (The encoding `<literal remap="tt">microsoft-symbol</literal>' doesn't make sense for Type 1 fonts). -</Para> +</para> -<Para> +<para> 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 `<Literal remap="tt">microsoft-symbol</Literal>', `<Literal remap="tt">microsoft-cp1252</Literal>', -`<Literal remap="tt">microsoft-win3.1</Literal>', or `<Literal remap="tt">apple-roman</Literal>' should yield reasonable +so one of `<literal remap="tt">microsoft-symbol</literal>', `<literal remap="tt">microsoft-cp1252</literal>', +`<literal remap="tt">microsoft-win3.1</literal>', or `<literal remap="tt">apple-roman</literal>' should yield reasonable results. -</Para> +</para> -</Sect4> +</sect4> -<Sect4> -<Title>Specifying an <Emphasis remap="it">ad hoc</Emphasis> encoding file</Title> +<sect4> +<title>Specifying an <emphasis remap="it">ad hoc</emphasis> encoding file</title> -<Para> +<para> It is always possible to define an encoding file to put the glyphs in a font in any desired order. Again, see the -`<Literal remap="tt">encodings/adobe-dingbats.enc</Literal>' file to see how this is done. -</Para> +`<filename>encodings/adobe-dingbats.enc</filename>' file to see how this is done. +</para> -</Sect4> +</sect4> -<Sect4> -<Title>Specifying font aliases</Title> +<sect4> +<title>Specifying font aliases</title> -<Para> +<para> By following the directions above, you will find yourself with a number of fonts with unusual names --- with encodings such as -`<Literal remap="tt">adobe-fontspecific</Literal>', `<Literal remap="tt">microsoft-win3.1</Literal>' <Emphasis remap="it">etc</Emphasis>. In order +`<literal remap="tt">adobe-fontspecific</literal>', `<literal remap="tt">microsoft-win3.1</literal>' <emphasis remap="it">etc</emphasis>. In order to use these fonts with standard applications, it may be useful to remap them to their proper names. -</Para> +</para> -<Para> -This is done by writing a `<Literal remap="tt">fonts.alias</Literal>' file. The format of this file +<para> +This is done by writing a `<filename>fonts.alias</filename>' 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 `<Literal remap="tt">fonts.alias</Literal>' file might look as follows: +name to a font name. A `<filename>fonts.alias</filename>' file might look as follows: -<Screen> +<screen> "-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" -</Screen> +</screen> (both XLFD names on a single line). The syntax of the -`<Literal remap="tt">fonts.alias</Literal>' file is more precisely described in the -<ULink -URL="mkfontdir.1.html" ->mkfontdir(1)</ULink +`<filename>fonts.alias</filename>' file is more precisely described in the +<ulink +url="mkfontdir.1.html" +>mkfontdir(1)</ulink > manual page. -</Para> +</para> -</Sect4> +</sect4> -</Sect3> +</sect3> -</Sect2> +</sect2> -<Sect2> -<Title>Additional notes about scalable core fonts</Title> +<sect2> +<title>Additional notes about scalable core fonts</title> -<Sect3> -<Title>About the <Emphasis remap="it">FreeType</Emphasis> backend</Title> +<sect3> +<title>About the <emphasis remap="it">FreeType</emphasis> backend</title> -<Para> -The <Emphasis remap="it">FreeType</Emphasis> backend (formerly <Emphasis remap="it">xfsft</Emphasis>) -is a backend based on version 2 of the FreeType library (see <ULink -URL="http://www.freetype.org/" ->the FreeType web site</ULink +<para> +The <emphasis remap="it">FreeType</emphasis> backend (formerly <emphasis remap="it">xfsft</emphasis>) +is a backend based on version 2 of the FreeType library (see <ulink +url="http://www.freetype.org/" +>the FreeType web site</ulink >) and has the X-TT functionalities for CJKV support provided by the After X-TT -Project (see <ULink -URL="http://x-tt.sourceforge.jp/" ->the After X-TT Project web site</ULink ->). The <Emphasis remap="it">FreeType</Emphasis> backend has support for the -``fontenc'' style of internationalisation (see <XRef LinkEnd="sec-fontenc">). This backend supports TrueType font files -(`<Literal remap="tt">*.ttf</Literal>'), OpenType font files (`<Literal remap="tt">*.otf</Literal>'), TrueType Collections -(`<Literal remap="tt">*.ttc</Literal>'), OpenType Collections (`<Literal remap="tt">*.otc</Literal>') and Type 1 font -files (`<Literal remap="tt">*.pfa</Literal>' and `<Literal remap="tt">*.pfb</Literal>'). -</Para> - -<Para> +Project (see <ulink +url="http://x-tt.sourceforge.jp/" +>the After X-TT Project web site</ulink +>). The <emphasis remap="it">FreeType</emphasis> backend has support for the +``fontenc'' style of internationalisation (see <xref linkend="sec-fontenc"/>). This backend supports TrueType font files +(`<filename>*.ttf</filename>'), OpenType font files (`<filename>*.otf</filename>'), TrueType Collections +(`<filename>*.ttc</filename>'), OpenType Collections (`<filename>*.otc</filename>') and Type 1 font +files (`<filename>*.pfa</filename>' and `<filename>*.pfb</filename>'). +</para> + +<para> 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, -</Para> +</para> -<Para> +<para> -<Screen> +<screen> :1:mincho.ttc -misc-pmincho-medium-r-normal--0-0-0-0-p-0-jisx0208.1990-0 -</Screen> +</screen> -</Para> +</para> -<Para> -refers to face 1 in the `<Literal remap="tt">mincho.ttc</Literal>' TrueType Collection file. -</Para> +<para> +refers to face 1 in the `<filename>mincho.ttc</filename>' TrueType Collection file. +</para> -<Para> -The new <Emphasis remap="it">FreeType</Emphasis> backend supports the extended -`<Literal remap="tt">fonts.dir</Literal>' syntax introduced by X-TrueType with a number +<para> +The new <emphasis remap="it">FreeType</emphasis> backend supports the extended +`<filename>fonts.dir</filename>' syntax introduced by X-TrueType with a number of options, collectively known as `TTCap'. A `TTCap' entry follows the general syntax -</Para> +</para> -<Para> +<para> -<Screen> +<screen> option=value: -</Screen> +</screen> -</Para> +</para> -<Para> -and should be specified before the filename. The new <Emphasis remap="it">FreeType</Emphasis> +<para> +and should be specified before the filename. The new <emphasis remap="it">FreeType</emphasis> almost perfectly supports TTCap options that are compatible with X-TT -1.4. The Automatic Italic (`<Literal remap="tt">ai</Literal>'), Double Strike (`<Literal remap="tt">ds</Literal>') and -Bounding box Width (`<Literal remap="tt">bw</Literal>') options are indispensable in CJKV. +1.4. The Automatic Italic (`<literal remap="tt">ai</literal>'), Double Strike (`<literal remap="tt">ds</literal>') and +Bounding box Width (`<literal remap="tt">bw</literal>') options are indispensable in CJKV. For example, -</Para> +</para> -<Para> +<para> -<Screen> +<screen> 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 @@ -1583,372 +1579,372 @@ 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 -</Screen> +</screen> -</Para> +</para> -<Para> +<para> setup the complete combination of jisx0208 and jisx0201 using mincho.ttc -only. More information on the TTCap syntax is found on <ULink -URL="http://x-tt.sourceforge.jp/" ->the After X-TT Project page</ULink +only. More information on the TTCap syntax is found on <ulink +url="http://x-tt.sourceforge.jp/" +>the After X-TT Project page</ulink >. -</Para> +</para> -<Para> -The <Emphasis remap="it">FreeType</Emphasis> backend uses the <Emphasis remap="it">fontenc</Emphasis> layer in order to support -recoding of fonts; this was described in <XRef LinkEnd="sec-fontenc"> and especially <XRef LinkEnd="sec-fontenc-freetype"> earlier in this document. -</Para> +<para> +The <emphasis remap="it">FreeType</emphasis> backend uses the <emphasis remap="it">fontenc</emphasis> layer in order to support +recoding of fonts; this was described in <xref linkend="sec-fontenc"/> and especially <xref linkend="sec-fontenc-freetype"/> earlier in this document. +</para> -</Sect3> +</sect3> -<Sect3> -<Title>Delayed glyph rasterisation</Title> +<sect3> +<title>Delayed glyph rasterisation</title> -<Para> +<para> When loading a proportional fonts which contain a huge number of glyphs, -the old <Emphasis remap="it">FreeType</Emphasis> delayed glyph rasterisation until the time at which +the old <emphasis remap="it">FreeType</emphasis> 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 <Emphasis remap="it">X-TT</Emphasis> module also -has this method, the "<Literal remap="tt">vl=y</Literal>" TTCap option must be set if you want to -use it. This is the default method for <Emphasis remap="it">FreeType</Emphasis> when it loads +loading TrueType or OpenType fonts. Although the <emphasis remap="it">X-TT</emphasis> module also +has this method, the "<literal remap="tt">vl=y</literal>" TTCap option must be set if you want to +use it. This is the default method for <emphasis remap="it">FreeType</emphasis> 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 <Emphasis remap="it">FreeType</Emphasis> backend -- its `very lazy' method is super-fast. -</Para> +the new <emphasis remap="it">FreeType</emphasis> backend -- its `very lazy' method is super-fast. +</para> -<Para> +<para> 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 `<Literal remap="tt">vl=y</Literal>' option, a chipped bitmap is displayed +backend is used with the `<literal remap="tt">vl=y</literal>' 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 `<Literal remap="tt">vl=n</Literal>' in the TTCap option to +method when using multi-bytes fonts, set `<literal remap="tt">vl=n</literal>' in the TTCap option to disable it: -</Para> +</para> -<Para> +<para> -<Screen> +<screen> vl=n:luxirr.ttf -b&h-Luxi Serif-medium-r-normal--0-0-0-0-p-0-iso10646-1 -</Screen> +</screen> -</Para> +</para> -<Para> +<para> 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 `<Literal remap="tt">c</Literal>', as in -</Para> +with an XLFD specifying a character-cell spacing `<literal remap="tt">c</literal>', as in +</para> -<Para> +<para> -<Screen> +<screen> -misc-mincho-medium-r-normal--0-0-0-0-c-0-jisx0208.1990-0 -</Screen> +</screen> -</Para> +</para> -<Para> +<para> or -</Para> +</para> -<Para> +<para> -<Screen> +<screen> fs=c:mincho.ttc -misc-mincho-medium-r-normal--0-0-0-0-p-0-jisx0208.1990-0 -</Screen> +</screen> -</Para> +</para> -<Para> +<para> 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. -</Para> +</para> -</Sect3> +</sect3> -</Sect2> +</sect2> -</Sect1> +</sect1> -<Sect1 id="sec-background" xreflabel="Appendix: Background"> -<Title>Appendix: background and terminology </Title> +<sect1 id="sec-background" xreflabel="Appendix: Background"> +<title>Appendix: background and terminology </title> -<Sect2> -<Title>Characters and glyphs</Title> +<sect2> +<title>Characters and glyphs</title> -<Para> +<para> A computer text-processing system inputs keystrokes and outputs -<Emphasis remap="it">glyphs</Emphasis>, small pictures that are assembled on paper or on a +<emphasis remap="it">glyphs</emphasis>, 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 <<Literal remap="tt">f</Literal>><<Literal remap="tt">i</Literal>> will typically +sequence of two keystrokes <<literal remap="tt">f</literal>><<literal remap="tt">i</literal>> 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. -</Para> +</para> -<Para> +<para> The complex transformation rules from keystrokes to glyphs are usually factored into two simpler transformations, from keystrokes to -<Emphasis remap="it">characters</Emphasis> and from characters to glyphs. You may want to think -of characters as the basic unit of text that is stored <Emphasis remap="it">e.g.</Emphasis> in +<emphasis remap="it">characters</emphasis> and from characters to glyphs. You may want to think +of characters as the basic unit of text that is stored <emphasis remap="it">e.g.</emphasis> 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. -</Para> +</para> -<Para> -A <Emphasis remap="it">coded character set</Emphasis> is a set of characters together with a -mapping from integer codes --- known as <Emphasis remap="it">codepoints</Emphasis> --- to +<para> +A <emphasis remap="it">coded character set</emphasis> is a set of characters together with a +mapping from integer codes --- known as <emphasis remap="it">codepoints</emphasis> --- to characters. Examples of coded character sets include US-ASCII, ISO 8859-1, KOI8-R, and JIS X 0208(1990). -</Para> +</para> -<Para> +<para> 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. -</Para> +</para> -</Sect2> +</sect2> -<Sect2 id="sec-xlfd"> -<Title>Font files, fonts, and XLFD </Title> +<sect2 id="sec-xlfd"> +<title>Font files, fonts, and XLFD </title> -<Para> -Traditionally, typographers speak about <Emphasis remap="it">typefaces</Emphasis> and -<Emphasis remap="it">founts</Emphasis>. A typeface is a particular style or design, such as +<para> +Traditionally, typographers speak about <emphasis remap="it">typefaces</emphasis> and +<emphasis remap="it">founts</emphasis>. 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. -</Para> +</para> -<Para> -Digital fonts come in <Emphasis remap="it">font files</Emphasis>. A font file contains the +<para> +Digital fonts come in <emphasis remap="it">font files</emphasis>. 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. -</Para> +</para> -<Para> +<para> Digital fonts may consist of bitmap data, in which case they are said -to be <Emphasis remap="it">bitmap fonts</Emphasis>. They may also consist of a mathematical +to be <emphasis remap="it">bitmap fonts</emphasis>. They may also consist of a mathematical description of glyph shapes, in which case they are said to be -<Emphasis remap="it">scalable fonts</Emphasis>. Common formats for scalable font files are -<Emphasis remap="it">Type 1</Emphasis> (sometimes incorrectly called <Emphasis remap="it">ATM fonts</Emphasis> or -<Emphasis remap="it">PostScript fonts</Emphasis>), <Emphasis remap="it">TrueType</Emphasis> and <Emphasis remap="it">OpenType</Emphasis>. -</Para> +<emphasis remap="it">scalable fonts</emphasis>. Common formats for scalable font files are +<emphasis remap="it">Type 1</emphasis> (sometimes incorrectly called <emphasis remap="it">ATM fonts</emphasis> or +<emphasis remap="it">PostScript fonts</emphasis>), <emphasis remap="it">TrueType</emphasis> and <emphasis remap="it">OpenType</emphasis>. +</para> -<Para> +<para> 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 1 fonts, glyphs are identified by <Emphasis remap="it">glyph names</Emphasis>. In the +Type 1 fonts, glyphs are identified by <emphasis remap="it">glyph names</emphasis>. In the case of TrueType fonts, glyphs are indexed by integers corresponding to one of a number of indexing schemes (usually Unicode --- see below). -</Para> +</para> -<Para> +<para> The X11 core fonts system uses the data in a font file to generate -<Emphasis remap="it">font instances</Emphasis>, which are collections of glyphs at a given size +<emphasis remap="it">font instances</emphasis>, which are collections of glyphs at a given size indexed according to a given encoding. -</Para> +</para> -<Para> +<para> X11 core font instances are usually specified using a notation known -as the <Emphasis remap="it">X Logical Font Description</Emphasis> (XLFD). An XLFD starts with a -dash `<Literal remap="tt">-</Literal>', and consists of fourteen fields separated by dashes, +as the <emphasis remap="it">X Logical Font Description</emphasis> (XLFD). An XLFD starts with a +dash `<literal remap="tt">-</literal>', and consists of fourteen fields separated by dashes, for example: -<Screen> +<screen> -adobe-courier-medium-r-normal--12-120-75-75-m-70-iso8859-1 -</Screen> +</screen> -Or particular interest are the last two fields `<Literal remap="tt">iso8859-1</Literal>', which +Or particular interest are the last two fields `<literal remap="tt">iso8859-1</literal>', which specify the font instance's encoding. -</Para> +</para> -<Para> +<para> A scalable font is specified by an XLFD which contains zeroes instead of some fields: -<Screen> +<screen> -adobe-courier-medium-r-normal--0-0-0-0-m-0-iso8859-1 -</Screen> +</screen> -</Para> +</para> -<Para> +<para> 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 `<Literal remap="tt">fixed</Literal>', which specifies the fallback font to -use when the requested font cannot be opened, and `<Literal remap="tt">cursor</Literal>', which +opened. These are `<literal remap="tt">fixed</literal>', which specifies the fallback font to +use when the requested font cannot be opened, and `<literal remap="tt">cursor</literal>', which specifies the set of glyphs to be used by the mouse pointer. -</Para> +</para> -<Para> +<para> Short names are usually implemented as aliases to XLFDs; the -standard `<Literal remap="tt">fixed</Literal>' and `<Literal remap="tt">cursor</Literal>' aliases are defined in +standard `<literal remap="tt">fixed</literal>' and `<literal remap="tt">cursor</literal>' aliases are defined in -<Screen> +<screen> /usr/share/font/X11/misc/fonts.alias -</Screen> +</screen> -</Para> +</para> -</Sect2> +</sect2> -<Sect2> -<Title>Unicode</Title> +<sect2> +<title>Unicode</title> -<Para> -Unicode (<ULink -URL="http://www.unicode.org" ->http://www.unicode.org</ULink +<para> +Unicode (<ulink +url="http://www.unicode.org" +>http://www.unicode.org</ulink >) 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. -</Para> +</para> -<Para> -Unicode is an <Emphasis remap="it">open</Emphasis> character set, meaning that codepoint +<para> +Unicode is an <emphasis remap="it">open</emphasis> 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 <Emphasis remap="it">sparse</Emphasis>, meaning that it only defines glyphs +Unicode font will be <emphasis remap="it">sparse</emphasis>, meaning that it only defines glyphs for a subset of the character registry of Unicode. -</Para> +</para> -<Para> +<para> The Unicode standard is defined in parallel with the international standard ISO 10646. Assignments in the two standards are always -equivalent, and we often use the terms <Emphasis remap="it">Unicode</Emphasis> and -<Emphasis remap="it">ISO 10646</Emphasis> interchangeably. -</Para> +equivalent, and we often use the terms <emphasis remap="it">Unicode</emphasis> and +<emphasis remap="it">ISO 10646</emphasis> interchangeably. +</para> -<Para> +<para> When used in the X11 core fonts system, Unicode-encoded fonts should -have the last two fields of their XLFD set to `<Literal remap="tt">iso10646-1</Literal>'. -</Para> +have the last two fields of their XLFD set to `<literal remap="tt">iso10646-1</literal>'. +</para> -</Sect2> +</sect2> -</Sect1> +</sect1> -<Sect1> -<Title>References</Title> +<sect1> +<title>References</title> -<Para> +<para> X11R&relvers; comes with extensive documentation in the form of manual pages and typeset documents. Before installing fonts, you really should -read the <ULink -URL="fontconfig.3.html" ->fontconfig(3)</ULink +read the <ulink +url="fontconfig.3.html" +>fontconfig(3)</ulink > and -<ULink -URL="mkfontdir.1.html" ->mkfontdir(1)</ULink +<ulink +url="mkfontdir.1.html" +>mkfontdir(1)</ulink > manual pages; other -manual pages of interest include <ULink -URL="X.7.html" ->X(7)</ULink +manual pages of interest include <ulink +url="X.7.html" +>X(7)</ulink >, -<ULink -URL="Xserver.1.html" ->Xserver(1)</ULink ->, <ULink -URL="xset.1.html" ->xset(1)</ULink ->, <ULink -URL="Xft.3.html" ->Xft(3)</ULink ->, <ULink -URL="xlsfonts.1.html" ->xlsfonts(1)</ULink -> and <ULink -URL="showfont.1.html" ->showfont(1)</ULink +<ulink +url="Xserver.1.html" +>Xserver(1)</ulink +>, <ulink +url="xset.1.html" +>xset(1)</ulink +>, <ulink +url="Xft.3.html" +>Xft(3)</ulink +>, <ulink +url="xlsfonts.1.html" +>xlsfonts(1)</ulink +> and <ulink +url="showfont.1.html" +>showfont(1)</ulink >. In addition, you may want to read the X Logical Font Description document, by Jim Flowers, which is provided in the file -`<Literal remap="tt">xc/doc/xlfd.PS.Z</Literal>'. -</Para> +`<filename>xc/doc/xlfd.PS.Z</filename>'. +</para> -<Para> -The <ULink -URL="http://www.faqs.org/faqs/by-newsgroup/comp/comp.fonts.html" ->comp.fonts FAQ</ULink +<para> +The <ulink +url="http://www.faqs.org/faqs/by-newsgroup/comp/comp.fonts.html" +>comp.fonts FAQ</ulink >, which is unfortunately no longer being maintained, contains a wealth of information about digital fonts. -</Para> +</para> -<Para> +<para> Xft and Fontconfig are described on -<ULink -URL="http://www.fontconfig.org" ->Keith Packard's Fontconfig site</ULink +<ulink +url="http://www.fontconfig.org" +>Keith Packard's Fontconfig site</ulink >. -</Para> +</para> -<Para> +<para> The -<ULink -URL="http://www.dcs.ed.ac.uk/home/jec/programs/xfsft/" ->xfsft home page</ULink +<ulink +url="http://www.dcs.ed.ac.uk/home/jec/programs/xfsft/" +>xfsft home page</ulink > has been superseded by this document, and is now obsolete; you may however still find some of the information that it contains useful. -<ULink -URL="http://www.joerg-pommnitz.de/TrueType/xfsft.html" ->Joerg Pommnitz' xfsft page</ULink +<ulink +url="http://www.joerg-pommnitz.de/TrueType/xfsft.html" +>Joerg Pommnitz' xfsft page</ulink > -is the canonical source for the `<Literal remap="tt">ttmkfdir</Literal>' utility, which is the -ancestor of <Literal remap="tt">mkfontscale</Literal>. -</Para> - -<Para> -<ULink -URL="http://www.pps.jussieu.fr/~jch/software/" ->The author's software pages</ULink +is the canonical source for the `<command>ttmkfdir</command>' utility, which is the +ancestor of <command>mkfontscale</command>. +</para> + +<para> +<ulink +url="http://www.pps.jussieu.fr/~jch/software/" +>The author's software pages</ulink > might or might not contain related scribbles and development versions of software. -</Para> +</para> -<Para> -The documentation of <Emphasis remap="it">X-TrueType</Emphasis> is available from <ULink -URL="http://x-tt.sourceforge.jp/" ->the After X-TT Project page</ULink +<para> +The documentation of <emphasis remap="it">X-TrueType</emphasis> is available from <ulink +url="http://x-tt.sourceforge.jp/" +>the After X-TT Project page</ulink >. -</Para> +</para> -<Para> -While the <ULink -URL="http://www.unicode.org" ->Unicode consortium site</ULink +<para> +While the <ulink +url="http://www.unicode.org" +>Unicode consortium site</ulink > may be of interest, you are more likely to find what you need in -Markus Kuhn's <ULink -URL="http://www.cl.cam.ac.uk/~mgk25/unicode.html" ->UTF-8 and Unicode FAQ</ULink +Markus Kuhn's <ulink +url="http://www.cl.cam.ac.uk/~mgk25/unicode.html" +>UTF-8 and Unicode FAQ</ulink >. -</Para> +</para> -<Para> +<para> 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 373. -</Para> +</para> -</Sect1> +</sect1> -</Article> +</article> diff --git a/sgml/Makefile.am b/sgml/Makefile.am index 9053ca0..eb094ae 100644 --- a/sgml/Makefile.am +++ b/sgml/Makefile.am @@ -20,7 +20,7 @@ # # Process this file with autoconf to create configure. -SUBDIRS = fonts platforms +SUBDIRS = platforms x11docdir = $(docdir) SGML_FILES = \ diff --git a/sgml/fonts/Makefile.am b/sgml/fonts/Makefile.am deleted file mode 100644 index 36392d6..0000000 --- a/sgml/fonts/Makefile.am +++ /dev/null @@ -1,5 +0,0 @@ -# Process this file with automake to create Makefile.in - -x11docdir = $(docdir)/fonts -SGML_FILES = fonts.sgml -include $(top_srcdir)/sgmlrules.in |