LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

updated XWindow-User-HOWTO, author of the update: mr. krzysztof zelechowski

This commit is contained in:
serek 2011-01-14 15:47:42 +00:00
parent 0f6c910e21
commit a8ae2a9ebf
1 changed files with 196 additions and 122 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

318
LDP/howto/docbook/XWindow-User-HOWTO.sgml → LDP/howto/docbook/XWindow-User-HOWTO.xml
View File

@ -1,4 +1,7 @@
<!DOCTYPE Article PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
>
<article id="index.html">
@ -6,9 +9,18 @@
<title>The X Window User HOWTO</title>
<pubdate>v3.1 10 October 2002</pubdate>
<pubdate>v4.0 Jan.&nbsp;12th, 2010</pubdate>
<authorgroup>
<author>
<firstname>Christopher</firstname>
<surname>Yeleighton</surname>
<affiliation>
<address>
<email>x11user@tldp.org</email>
</address>
</affiliation>
</author>
<author>
<firstname>Hal</firstname>
<surname>Burgiss</surname>
@ -21,13 +33,18 @@
</authorgroup>
<revhistory>
<revision
><revnumber>v4.0</revnumber
><date>2010-01-12</date><authorinitials>cy</authorinitials
><revremark>Converted to XML docbook and to the new domain.</revremark
></revision>
<revision>
<revnumber>v3.1</revnumber>
<date>2002-10-10</date>
<authorinitials>hb</authorinitials>
<revremark>
Some minor additions and updates.
</Revremark>
</revremark>
</revision>
<revision>
<revnumber>v3.0</revnumber>
@ -35,7 +52,7 @@
<authorinitials>hb</authorinitials>
<revremark>
Rewrite of the original document. Convert to DocBook. Many, many changes.
</Revremark>
</revremark>
</revision>
</revhistory>
@ -56,8 +73,8 @@
<abstract>
<para>
<remark>
<remark><literallayout>
<![CDATA[
v4.x changes:
- artheader tag changed to articleinfo
- graphic tag is being depricated in DocBook 5.x. To prepare for
@ -190,8 +207,8 @@ submit:
@echo "Updated and ready: $(SRC_URL)" |\
mail -s "$(TITLE) update" submit@linuxdoc.org &&\
echo " $(TITLE) Submitted!"
</remark>
]]>
</literallayout></remark>
</para>
@ -331,10 +348,12 @@ submit:
<title>New Versions and ChangeLog</title>
<para>
The current official version of this HOWTO may be found at the Linux Documentation Project, <ulink
url="http://www.linuxdoc.org/HOWTO/XWindow-User-HOWTO.html">http://www.linuxdoc.org/HOWTO/XWindow-User-HOWTO.html</ulink>.
Pre-release versions may be periodically posted to <ulink
url="http://feenix.burgiss.net/ldp/x-user/">http://feenix.burgiss.net/ldp/x-user/</ulink>.
The <ulink
url="http://tldp.org/HOWTO/XWindow-User-HOWTO.html"
>current official version of this HOWTO </ulink>
may be found at the Linux Documentation Project.
</para>
<para>
@ -852,7 +871,7 @@ submit:
run after installation if need be, to alter the configuration, or if new
hardware is installed. Read your locally installed documentation first. If
you attempt to hand edit this file, be sure to make a backup copy first since
<application>X</application> won't start if this file is not to its liking
<application>X</application> will not start if this file is not to its liking
;-)
</para>
@ -1065,9 +1084,14 @@ EndSection
<para>
Explicit <quote>Modeline</quote> definitions are not required as of 4.x ;-)
This sometimes required hand editing to get optimal values in earlier versions of
XFree86, though is generally not necessary with v4.x. <citetitle>The XFree86 Video
Timings HOWTO</citetitle>, <ulink
url="http://www.linuxdoc.org/HOWTO/XFree86-Video-Timings-HOWTO/index.html">http://www.linuxdoc.org/HOWTO/XFree86-Video-Timings-HOWTO/index.html</ulink>
XFree86, though is generally not necessary with v4.x.
<ulink
url="http://tldp.org/HOWTO/XFree86-Video-Timings-HOWTO/index.html"
>The XFree86 Video
Timings HOWTO
</ulink>
has a nice, but rather technical, explanation of this.
</para>
@ -1168,9 +1192,12 @@ EndSection
<para>
The last line is the <quote>Modeline</quote> being used to drive the current
screen. See <citetitle>The XFree86 Video
Timings HOWTO</citetitle>, <ulink
url="http://www.linuxdoc.org/HOWTO/XFree86-Video-Timings-HOWTO/index.html">http://www.linuxdoc.org/HOWTO/XFree86-Video-Timings-HOWTO/index.html</ulink>,
screen. See <ulink
url="http://tldp.org/HOWTO/XFree86-Video-Timings-HOWTO/index.html"
>The XFree86 Video
Timings HOWTO
</ulink>,
for more on <quote>Modelines</quote>.
@ -1406,7 +1433,7 @@ EndSection
<para>
<screen>
<![CDATA[
#!/bin/sh
# $XConsortium: xinitrc.cpp,v 1.4 91/08/22 11:41:34 rws Exp $
@ -1457,7 +1484,7 @@ else
fi
#eof
]]>
</screen>
</para>
@ -1519,7 +1546,7 @@ fi
<para>
<screen>
<![CDATA[
#!/bin/bash
# ~/.Xclients, start my programs.
@ -1555,7 +1582,7 @@ exec twm >> ~/.wm-errors 2>&1
echo `date`: Unable to start a Window Manager ... |tee -a ~/.wm-errors 2>&1
# eof
]]>
</screen>
</para>
@ -1566,7 +1593,7 @@ echo `date`: Unable to start a Window Manager ... |tee -a ~/.wm-errors 2>&1
with even more setting up of the environment (monitor, mouse and keyboard) using
<command>xset</command> this time, and a different Window Manager than was
available with the system defaults. This is in the user's home directory, so
it won't be overwritten during upgrades too.
it will not be overwritten during upgrades too.
</para>
@ -1623,7 +1650,7 @@ echo `date`: Unable to start a Window Manager ... |tee -a ~/.wm-errors 2>&1
<para>
Display managers really do much more than enable GUI style log-ins. They
are also used to manage local as well as remote <quote>displays</quote> on a
network. We won't get into details on this here, but it is nicely covered in
network. We shall not get into details on this here, but it is nicely covered in
the <citetitle>Remote X Apps Mini HOWTO</citetitle> and the <citetitle>XDMCP
HOWTO</citetitle> (see the <link linkend="links">links section</link>). For
our purposes here, they provide similar services to <command>getty</command>
@ -1873,7 +1900,7 @@ echo `date`: Unable to start a Window Manager ... |tee -a ~/.wm-errors 2>&1
</para>
<para>
We won't include an <filename>~/.xsession</filename> example here, since it
We shall not include an <filename>~/.xsession</filename> example here, since it
would be very similar to the <filename>~/.xinitrc</filename> and
<filename>~/.Xclients</filename> examples above.
@ -2089,9 +2116,9 @@ echo `date`: Unable to start a Window Manager ... |tee -a ~/.wm-errors 2>&1
<para>
<screen>
<![CDATA[
xterm -bg blue &
]]>
</screen>
</para>
@ -2502,9 +2529,16 @@ echo `date`: Unable to start a Window Manager ... |tee -a ~/.wm-errors 2>&1
</para>
<para>
Setting up international keyboards in nicely discussed in <ulink
url="http://www.linuxdoc.org/HOWTO/mini/Intkeyb/index.html">http://www.linuxdoc.org/HOWTO/mini/Intkeyb/index.html</ulink>.
Also, a search of <ulink url="http://google.com/linux">http://google.com/linux</ulink>
A nice discussion of
<ulink
url="http://tldp.org/HOWTO/Intkeyb/index.html"
>setting up international keyboards
</ulink>.
Also,
<ulink url="http://google.com/linux"
>Google search</ulink>
will turn up many creative examples.
</para>
@ -2571,9 +2605,9 @@ echo `date`: Unable to start a Window Manager ... |tee -a ~/.wm-errors 2>&1
BIOS set up, or Linux set up before <application>X</application> starts. So the
trick above is one way. There is also a utility available as either
<application>numlockx</application>, or
<application>setnumlock</application>, that can be found on the 'Net, if
<application>setnumlock</application>, that can be found on the ’Net, if
your distribution does not include one or the other. This can be put in a
start up file to turn <literal>Numlock</literal> on automatically if you'd
start up file to turn <literal>Numlock</literal> on automatically if you would
prefer.
</para>
@ -2598,48 +2632,70 @@ echo `date`: Unable to start a Window Manager ... |tee -a ~/.wm-errors 2>&1
</para>
<para>
<itemizedlist>
<variablelist>
<listitem>
<para>
Ctrl-Alt-BackSpace - Will kill the X server process in an orderly
<varlistentry><term ><keycombo ><keycap >Ctrl</keycap >
<keycap >Alt</keycap > <keycap >BackSpace</keycap ></keycombo
></term >
<listitem ><para>
Will kill the <application>X</application> server process in an orderly
fashion. This is a quick, easy, legitimate way to restart
<application>X</application>. Note it does not restart the display
manager (if used) -- just <application>X</application> itself.
manager (if used) &mdash; just <application>X</application> itself.
</para>
</listitem>
</listitem> </varlistentry >
<listitem>
<varlistentry ><term ><keycombo ><keycap >Ctrl</keycap >
<keycap >Alt</keycap >
<keycap >F<replaceable >n</replaceable ></keycap ></keycombo
></term ><listitem>
<para>
Ctrl-Alt-Fx - where <quote>x</quote> corresponds to a valid tty number
(typically 1-6). This is typically used to jump to a text console login,
where <replaceable >n</replaceable >
corresponds to a valid <acronym >TTY</acronym > number
(typically 1&ndash;6).
This is typically used to jump to a text console login,
while <application>X</application> remains running. To get back to
<application>X</application>, then it is <quote>Alt-Fx</quote>. In this
case, <quote>x</quote> represents one plus the last tty (e.g. Alt-F7 if
there are six available ttys).
<application>X</application>,
press
<keycombo ><keycap >Alt</keycap >
<keycap >F<replaceable >n</replaceable ></keycap ></keycombo >. In this
case, <replaceable >n</replaceable>
represents one plus the last <acronym >TTY</acronym >
(e.g. <keycombo ><keycap >Alt</keycap > <keycap >F7</keycap ></keycombo > if
there are six available <acronym >TTY</acronym >&rsquo;s).
</para>
</listitem>
</listitem> </varlistentry >
<listitem>
<varlistentry
><term
><keycombo
><keycap
>Ctrl</keycap > <keycap >Alt</keycap > <keycap >+</keycap ></keycombo >
and <keycombo
><keycap
>Ctrl</keycap > <keycap >Alt</keycap > <keycap >-</keycap ></keycombo ></term
><listitem>
<para>
Ctrl-Alt-keypad+ and Ctrl-Alt-keypad- - That is the plus and minus keys on
That is the plus and minus keys on
the keypad. This will cycle through any existing valid screen resolution
<quote>Modes</quote>, e.g. 1024x768 -> 600x800. Note the actual screen
size is the same -- just the view and resolution changes. Not all that
modes, e.g. 1024&times;768 &rarr; 600&times;800. Note the actual screen
size is the same &mdash; just the view and resolution changes.
Not all that
useful for most purposes. You cannot permanently change the screen
resolution without restarting <application>X</application>.
</para>
</listitem>
</listitem> </varlistentry >
</itemizedlist>
</para>
</variablelist>
<para>
It's possible your Window Manager, Desktop Environment or other system
component may trap these, and alter the standard behavior. In addition, the
Ctrl-Alt-Delete may be trapped as well. This should shut
<keycombo
><keycap >Ctrl</keycap> <keycap>Alt</keycap>
<keycap >Delete</keycap></keycombo> may be trapped as well. This should shut
<application>X</application> (and the system) down orderly, if it is
available.
@ -3084,7 +3140,7 @@ echo `date`: Unable to start a Window Manager ... |tee -a ~/.wm-errors 2>&1
on. For example, open an <emphasis remap="bf">xterm</emphasis> window and
type in something like <literal remap="tt">xterm -font </literal> followed by
an opening quotation mark. Then point to that spot on your screen, and click
your middle mouse button (or click both the left and right, if you're
your middle mouse button (or click both the left and right, if you are
middle-button impaired). This will paste the selection from the clipboard,
which should be the font you just selected. Then enter the closing quote, and
hit <literal remap="tt">Enter</literal>. For instance, a nice big <emphasis
@ -3168,7 +3224,7 @@ echo `date`: Unable to start a Window Manager ... |tee -a ~/.wm-errors 2>&1
</para>
<para>
That's the bad news. The good news is that any TrueType font included with
That is the bad news. The good news is that any TrueType font included with
any version of Windows, or any Windows applications, should work on Linux.
Though you will have to take some additional steps to integrate them. This
particularly helps web browsing where <application>X's</application>
@ -3177,12 +3233,18 @@ echo `date`: Unable to start a Window Manager ... |tee -a ~/.wm-errors 2>&1
</para>
<para>
We won't go into detail on installing and configuring these fonts here, as it
is addressed in depth in other documents. See <citetitle>The Font HOWTO
</citetitle>, <ulink url="http://www.linuxdoc.org/HOWTO/Font-HOWTO.html"></ulink>,
for general font information, and Type 1 tips. See <citetitle>The Font De-Uglification
Mini HOWTO</citetitle>, <ulink
url="http://www.linuxdoc.org/HOWTO/mini/FDU/index.html">http://www.linuxdoc.org/HOWTO/mini/FDU/index.html</ulink>,
We shall not go into detail on installing and configuring these fonts here,
as it is addressed in depth in other documents. See
<ulink url="http://tldp.org/HOWTO/Font-HOWTO.html">The Font HOWTO</ulink>
for general font information, and Type 1 tips.
See <citetitle>The Font De-Uglification
Mini HOWTO</citetitle>,
<ulink
url="http://tldp.org/HOWTO/FDU/index.html"
>The Font De-Uglification
Mini HOWTO</ulink>,
for various <application>X</application> related font tips, especially TrueType.
</para>
@ -3288,7 +3350,7 @@ echo `date`: Unable to start a Window Manager ... |tee -a ~/.wm-errors 2>&1
<title>Window Managers and Desktops</title>
<para>
We won't delve into configuring Window Manager's and Desktop Environments.
We shall not delve into configuring Window Manager's and Desktop Environments.
There is just too much to try to cover in one document. It is important to
realize that the two are not the same. There are many, many Window Managers
available.
@ -3552,8 +3614,8 @@ echo `date`: Unable to start a Window Manager ... |tee -a ~/.wm-errors 2>&1
<para>
<variablelist>
<VarListEntry>
<Term>-display <emphasis>[host]:display[.screen]</emphasis></Term>
<varlistentry>
<term>-display <emphasis>[host]:display[.screen]</emphasis></term>
<listitem>
<para>
This option specifies the X server display to use. This is often used
@ -3563,10 +3625,10 @@ echo `date`: Unable to start a Window Manager ... |tee -a ~/.wm-errors 2>&1
variable, which uses the same syntax.
</para>
</listitem>
</VarListEntry>
</varlistentry>
<VarListEntry>
<Term>-geometry <emphasis>geometry</emphasis></Term>
<varlistentry>
<term>-geometry <emphasis>geometry</emphasis></term>
<listitem>
<para>
The initial size and location of the window, in a format such as
@ -3577,39 +3639,39 @@ echo `date`: Unable to start a Window Manager ... |tee -a ~/.wm-errors 2>&1
of from the top left corner.
</para>
</listitem>
</VarListEntry>
</varlistentry>
<VarListEntry>
<Term>-font <emphasis>fontname</emphasis></Term>
<varlistentry>
<term>-font <emphasis>fontname</emphasis></term>
<listitem>
<para>
The font to use for displaying the text in your window (see font section
below).
</para>
</listitem>
</VarListEntry>
</varlistentry>
<VarListEntry>
<Term>-bg <emphasis>color</emphasis></Term>
<varlistentry>
<term>-bg <emphasis>color</emphasis></term>
<listitem>
<para>
The color to use for the window background. Typically this is a
<quote>color name</quote> (see below).
</para>
</listitem>
</VarListEntry>
</varlistentry>
<VarListEntry>
<Term>-fg <emphasis>color</emphasis></Term>
<varlistentry>
<term>-fg <emphasis>color</emphasis></term>
<listitem>
<para>
The color to use for the window foreground (i.e. fonts, etc).
</para>
</listitem>
</VarListEntry>
</varlistentry>
<VarListEntry>
<Term>-name <emphasis>resource-name</emphasis></Term>
<varlistentry>
<term>-name <emphasis>resource-name</emphasis></term>
<listitem>
<para>
Useful for specifying the name under which the resources for this
@ -3621,10 +3683,10 @@ echo `date`: Unable to start a Window Manager ... |tee -a ~/.wm-errors 2>&1
the resource database.
</para>
</listitem>
</VarListEntry>
</varlistentry>
<VarListEntry>
<Term>-title <emphasis>string</emphasis></Term>
<varlistentry>
<term>-title <emphasis>string</emphasis></term>
<listitem>
<para>
This is the title to be used for the window on your display, generally used
@ -3632,19 +3694,19 @@ echo `date`: Unable to start a Window Manager ... |tee -a ~/.wm-errors 2>&1
Not to be confused with the <quote>-name</quote> option.
</para>
</listitem>
</VarListEntry>
</varlistentry>
<VarListEntry>
<Term>-iconic</Term>
<varlistentry>
<term>-iconic</term>
<listitem>
<para>
Open window in an iconified state.
</para>
</listitem>
</VarListEntry>
</varlistentry>
<VarListEntry>
<Term>-xrm <emphasis>resource-string</emphasis></Term>
<varlistentry>
<term>-xrm <emphasis>resource-string</emphasis></term>
<listitem>
<para>
This option specifies a resource name and value to override any defaults
@ -3655,7 +3717,7 @@ echo `date`: Unable to start a Window Manager ... |tee -a ~/.wm-errors 2>&1
functionally the same as <quote>xterm -bg blue &#38;</quote>.
</para>
</listitem>
</VarListEntry>
</varlistentry>
</variablelist>
</para>
@ -3756,7 +3818,7 @@ echo `date`: Unable to start a Window Manager ... |tee -a ~/.wm-errors 2>&1
reasonable way. The <quote>$TERM</quote> variable is actually a reference to
an entry in the <quote>termcap</quote> database (man termcap), which is
typically installed as <filename>/etc/termcap</filename>. Unless you are
doing something really unusual, you probably won't need to change this.
doing something really unusual, you probably will not need to change this.
Some additional terminal configuration can be done with the
<command>stty</command> command (see man page). Terminal configuration is
really beyond the scope of this document.
@ -3834,9 +3896,12 @@ echo `date`: Unable to start a Window Manager ... |tee -a ~/.wm-errors 2>&1
<para>
Both <application>X</application> networking and security are nicely covered
in <citetitle>The Remote X Apps Mini HOWTO</citetitle>, <ulink
url="http://www.linuxdoc.org/HOWTO/mini/Remote-X-Apps.html">http://www.linuxdoc.org/HOWTO/mini/Remote-X-Apps.html</ulink>,
so we won't need to try to rehash it here. Recommended reading. See other
in <ulink
url="http://tldp.org/HOWTO/Remote-X-Apps.html"
>The Remote X Apps Mini HOWTO
</ulink>,
so we shall not need to try to rehash it here. Recommended reading. See other
references in the <link linkend="links">Links section</link> of the
Appendix below.
@ -4294,14 +4359,14 @@ echo `date`: Unable to start a Window Manager ... |tee -a ~/.wm-errors 2>&1
</para>
<para>
This won't do much on systems that are mostly idle.
This will not do much on systems that are mostly idle.
</para>
<para>
This does not work so well with <command>startx</command> since
<application>X</application> runs as root, and you're not root, right? So
you'd have to use something like <command>sudo</command> to have this done
<application>X</application> runs as root, and you are not root, right? So
you would have to use something like <command>sudo</command> to have this done
automatically.
</para>
@ -4653,9 +4718,10 @@ echo `date`: Unable to start a Window Manager ... |tee -a ~/.wm-errors 2>&1
<listitem>
<para>
If you are just starting out, you may find the
<citetitle>X Window System Architecture Overview HOWTO
</citetitle>, <ulink
url="http://www.linuxdoc.org/HOWTO/XWindow-Overview-HOWTO/index.html">http://www.linuxdoc.org/HOWTO/XWindow-Overview-HOWTO/</ulink>
<ulink
url="http://tldp.org/HOWTO/XWindow-Overview-HOWTO/index.html"
>X Window System Architecture Overview HOWTO</ulink>
to be helpful. It covers all the basic concepts quite well.
</para>
@ -4663,8 +4729,9 @@ echo `date`: Unable to start a Window Manager ... |tee -a ~/.wm-errors 2>&1
<listitem>
<para>
<citetitle>The Remote X Apps Mini HOWTO</citetitle>,
<ulink url="http://www.linuxdoc.org/HOWTO/mini/Remote-X-Apps.html">http://www.linuxdoc.org/HOWTO/mini/Remote-X-Apps.html</ulink>,
<ulink url="http://tldp.org/HOWTO/Remote-X-Apps.html"
>The Remote X Apps Mini HOWTO
</ulink>
does a nice job of discussing running <application>X</application>
remotely, and related security issues of <application>X</application> networking.
</para>
@ -4672,63 +4739,70 @@ echo `date`: Unable to start a Window Manager ... |tee -a ~/.wm-errors 2>&1
<listitem>
<para>
<citetitle>The XDMCP HOWTO</citetitle>,
<ulink url="http://www.linuxdoc.org/HOWTO/XDMCP-HOWTO/index.html">http://www.linuxdoc.org/HOWTO/XDMCP-HOWTO/index.html</ulink>,
<ulink url="http://tldp.org/HOWTO/XDMCP-HOWTO/index.html"
>The XDMCP HOWTO
</ulink>
covers the X Display Manager Control Protocol, for running
<application>X</application> remotely. Also,
<citetitle>The XDM and X Terminal mini-HOWTO</citetitle>,
<ulink url="http://www.linuxdoc.org/HOWTO/mini/XDM-Xterm/index.html">http://www.linuxdoc.org/HOWTO/mini/XDM-Xterm/index.html</ulink>.
<ulink url="http://tldp.org/HOWTO/XDM-Xterm/index.html"
>The XDM and X Terminal mini-HOWTO
</ulink>.
</para>
</listitem>
<listitem>
<para>
<citetitle>The XFree86 HOWTO</citetitle>,
<ulink url="http://www.linuxdoc.org/HOWTO/XFree86-HOWTO/index.html">http://www.linuxdoc.org/HOWTO/XFree86-HOWTO/index.html</ulink>,
<ulink url="http://tldp.org/HOWTO/XFree86-HOWTO/index.html"
>The XFree86 HOWTO
</ulink>
succinctly covers installation, and initial configuration.
</para>
</listitem>
<listitem>
<para>
<citetitle>The XFree86 Video Timings HOWTO</citetitle>,
<ulink url="http://www.linuxdoc.org/HOWTO/XFree86-Video-Timings-HOWTO/index.html">http://www.linuxdoc.org/HOWTO/XFree86-Video-Timings-HOWTO/index.html</ulink>,
<ulink
url="http://tldp.org/HOWTO/XFree86-Video-Timings-HOWTO/index.html"
>The XFree86 Video Timings HOWTO
</ulink>
gets down and dirty with the finer points of monitor tuning. Generally
not required for XFree86 v4.x.
</para>
</listitem>
<listitem>
<para>
<citetitle>The Xinerama HOWTO</citetitle>,
<ulink url="http://www.linuxdoc.org/HOWTO/Xinerama-HOWTO.html">http://www.linuxdoc.org/HOWTO/Xinerama-HOWTO.html</ulink>,
<ulink url="http://tldp.org/HOWTO/Xinerama-HOWTO.html"
>The Xinerama HOWTO</ulink>
covers multi-headed displays.
</para>
</listitem>
<listitem>
<para>
<citetitle>The Font HOWTO</citetitle>,
<ulink url="http://www.linuxdoc.org/HOWTO/Font-HOWTO.html"></ulink>,
<ulink url="http://tldp.org/HOWTO/Font-HOWTO.html"
>The Font HOWTO</ulink>
covers various font topics.
</para>
</listitem>
<listitem>
<para>
<citetitle>The Font De-Uglification Mini HOWTO</citetitle>,
<ulink url="http://www.linuxdoc.org/HOWTO/mini/FDU/index.html">http://www.linuxdoc.org/HOWTO/mini/FDU/index.html</ulink>,
<ulink url="http://tldp.org/HOWTO/FDU/index.html"
>The Font De-Uglification Mini HOWTO
</ulink>
covers a range of <application>X</application> font issues.
</para>
</listitem>
<listitem>
<para>
<citetitle>The International Keyboard HOWTO</citetitle>;
<ulink url="http://www.linuxdoc.org/HOWTO/mini/Intkeyb/index.html">http://www.linuxdoc.org/HOWTO/mini/Intkeyb/index.html</ulink>
<ulink url="http://tldp.org/HOWTO/Intkeyb/index.html"
>The International Keyboard HOWTO
</ulink>
</para>
</listitem>
<listitem>
<para>
<citetitle>The Linux Infrared HOWTO</citetitle>:
<ulink url="http://www.linuxdoc.org/HOWTO/Infrared-HOWTO/index.html
">http://www.linuxdoc.org/HOWTO/Infrared-HOWTO/index.html </ulink>
<ulink url="http://tldp.org/HOWTO/Infrared-HOWTO/index.html"
>The Linux Infrared HOWTO
</ulink>
</para>
</listitem>
</itemizedlist>