From owner-svn-doc-head@FreeBSD.ORG Fri Aug 23 03:59:23 2013
Return-Path: <owner-svn-doc-head@FreeBSD.ORG>
Delivered-To: svn-doc-head@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTP id 9E3BB2AC;
Fri, 23 Aug 2013 03:59:23 +0000 (UTC)
(envelope-from wblock@FreeBSD.org)
Received: from svn.freebsd.org (svn.freebsd.org
[IPv6:2001:1900:2254:2068::e6a:0])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by mx1.freebsd.org (Postfix) with ESMTPS id 872552A5B;
Fri, 23 Aug 2013 03:59:23 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id r7N3xMu0057209;
Fri, 23 Aug 2013 03:59:22 GMT (envelope-from wblock@svn.freebsd.org)
Received: (from wblock@localhost)
by svn.freebsd.org (8.14.7/8.14.5/Submit) id r7N3xM5O057208;
Fri, 23 Aug 2013 03:59:22 GMT (envelope-from wblock@svn.freebsd.org)
Message-Id: <201308230359.r7N3xM5O057208@svn.freebsd.org>
From: Warren Block <wblock@FreeBSD.org>
Date: Fri, 23 Aug 2013 03:59:22 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
svn-doc-head@freebsd.org
Subject: svn commit: r42576 - head/en_US.ISO8859-1/books/handbook/x11
X-SVN-Group: doc-head
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-BeenThere: svn-doc-head@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: SVN commit messages for the doc tree for head
<svn-doc-head.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-head>,
<mailto:svn-doc-head-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-head>
List-Post: <mailto:svn-doc-head@freebsd.org>
List-Help: <mailto:svn-doc-head-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-head>,
<mailto:svn-doc-head-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 03:59:23 -0000
Author: wblock
Date: Fri Aug 23 03:59:22 2013
New Revision: 42576
URL: http://svnweb.freebsd.org/changeset/doc/42576
Log:
Whitespace-only fixes. Translators, please ignore.
Modified:
head/en_US.ISO8859-1/books/handbook/x11/chapter.xml
Modified: head/en_US.ISO8859-1/books/handbook/x11/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/handbook/x11/chapter.xml Fri Aug 23 02:14:23 2013 (r42575)
+++ head/en_US.ISO8859-1/books/handbook/x11/chapter.xml Fri Aug 23 03:59:22 2013 (r42576)
@@ -36,8 +36,8 @@
used by &os;.</para>
<para>For more information on the video hardware that X11
- supports, check the <ulink
- url="http://www.x.org/">&xorg;</ulink> web site.</para>
+ supports, check the
+ <ulink url="http://www.x.org/">&xorg;</ulink> web site.</para>
<para>After reading this chapter, you will know:</para>
@@ -97,11 +97,12 @@
<quote>Window</quote>). X was just the next letter in the
Roman alphabet.</para>
- <para>X can be called <quote>X</quote>, <quote>X Window
- System</quote>, <quote>X11</quote>, and a number of other
- terms. You may find that using the term <quote>X
- Windows</quote> to describe X11 can be offensive to some
- people; for a bit more insight on this, see &man.X.7;.</para>
+ <para>X can be called <quote>X</quote>,
+ <quote>X Window System</quote>, <quote>X11</quote>, and a
+ number of other terms. You may find that using the term
+ <quote>X Windows</quote> to describe X11 can be offensive to
+ some people; for a bit more insight on this, see
+ &man.X.7;.</para>
</sect2>
<sect2>
@@ -110,21 +111,20 @@
<para>X was designed from the beginning to be network-centric,
and adopts a <quote>client-server</quote> model.</para>
- <para>In the X model, the
- <quote>X server</quote> runs on the computer that has the
- keyboard, monitor, and mouse attached. The server's
- responsibility includes tasks such as managing the
- display, handling input from the keyboard and mouse, and
+ <para>In the X model, the <quote>X server</quote> runs on the
+ computer that has the keyboard, monitor, and mouse attached.
+ The server's responsibility includes tasks such as managing
+ the display, handling input from the keyboard and mouse, and
other input or output devices (i.e., a <quote>tablet</quote>
- can be used as an input device, and a video projector
- may be an alternative output device). Each X application
- (such as <application>XTerm</application> or
+ can be used as an input device, and a video projector may be
+ an alternative output device). Each X application (such as
+ <application>XTerm</application> or
<application>Firefox</application>) is a
- <quote>client</quote>. A client sends messages to the server
- such as <quote>Please draw a window at these
- coordinates</quote>, and the server sends back messages such
- as <quote>The user just clicked on the OK
- button</quote>.</para>
+ <quote>client</quote>. A client sends messages to the server
+ such as
+ <quote>Please draw a window at these coordinates</quote>, and
+ the server sends back messages such as
+ <quote>The user just clicked on the OK button</quote>.</para>
<para>In a home or small office environment, the X server and
the X clients commonly run on the same computer. However, it
@@ -177,16 +177,15 @@
application called a <quote>Window Manager</quote>. There
are <ulink
url="http://xwinman.org/">dozens of window managers</ulink>
- available for X. Each of
- these window managers provides a different look and feel;
- some of them support <quote>virtual desktops</quote>; some
- of them allow customized keystrokes to manage the desktop;
- some have a <quote>Start</quote> button or similar device;
- some are <quote>themeable</quote>, allowing a complete change
- of look-and-feel by applying a new theme. Window managers
- are available in the
- <filename>x11-wm</filename> category of the Ports
- Collection.</para>
+ available for X. Each of these window managers provides a
+ different look and feel; some of them support
+ <quote>virtual desktops</quote>; some of them allow customized
+ keystrokes to manage the desktop; some have a
+ <quote>Start</quote> button or similar device; some are
+ <quote>themeable</quote>, allowing a complete change of
+ look-and-feel by applying a new theme. Window managers are
+ available in the <filename>x11-wm</filename> category of the
+ Ports Collection.</para>
<para>In addition, the <application>KDE</application> and
<application>GNOME</application> desktop environments both
@@ -203,14 +202,14 @@
<note>
<title>Focus Policy</title>
- <para>Another feature the window manager is responsible for
- is the mouse <quote>focus policy</quote>. Every windowing
+ <para>Another feature the window manager is responsible for is
+ the mouse <quote>focus policy</quote>. Every windowing
system needs some means of choosing a window to be actively
receiving keystrokes, and should visibly indicate which
window is active as well.</para>
<para>A familiar focus policy is called
- <quote>click-to-focus</quote>. This is the model utilized
+ <quote>click-to-focus</quote>. This is the model utilized
by µsoft.windows;, in which a window becomes active
upon receiving a mouse click.</para>
@@ -326,28 +325,26 @@
available.</para>
</note>
- <para>Alternatively, X11
- can be installed directly from packages.
+ <para>Alternatively, X11 can be installed directly from packages.
Binary packages to use with &man.pkg.add.1; tool are also
available for X11. When the remote fetching feature of
- &man.pkg.add.1; is used, the version number of the package
- must be removed. &man.pkg.add.1; will automatically fetch
- the latest version of the application.</para>
+ &man.pkg.add.1; is used, the version number of the package must
+ be removed. &man.pkg.add.1; will automatically fetch the latest
+ version of the application.</para>
<para>So to fetch and install the package of
<application>&xorg;</application>, simply type:</para>
<screen>&prompt.root; <userinput>pkg_add -r xorg</userinput></screen>
- <note><para>The examples above will install the complete
- X11 distribution including the
- servers, clients, fonts etc. Separate packages and ports of X11
- are also
- available.</para>
-
- <para>To install a minimal X11 distribution you can
- alternatively install
- <filename role="package">x11/xorg-minimal</filename>.</para>
+ <note>
+ <para>The examples above will install the complete X11
+ distribution including the servers, clients, fonts etc.
+ Separate packages and ports of X11 are also available.</para>
+
+ <para>To install a minimal X11 distribution you can
+ alternatively install
+ <filename role="package">x11/xorg-minimal</filename>.</para>
</note>
<para>The rest of this chapter will explain how to configure
@@ -368,7 +365,6 @@
</sect1info>
<title>X11 Configuration</title>
-
<indexterm><primary>&xorg;</primary></indexterm>
<indexterm><primary>X11</primary></indexterm>
@@ -380,9 +376,17 @@
hardware information before beginning configuration.</para>
<itemizedlist>
- <listitem><para>Monitor sync frequencies</para></listitem>
- <listitem><para>Video card chipset</para></listitem>
- <listitem><para>Video card memory</para></listitem>
+ <listitem>
+ <para>Monitor sync frequencies</para>
+ </listitem>
+
+ <listitem>
+ <para>Video card chipset</para>
+ </listitem>
+
+ <listitem>
+ <para>Video card memory</para>
+ </listitem>
</itemizedlist>
<indexterm>
@@ -421,13 +425,13 @@
<sect2>
<title>Configuring X11</title>
- <para><application>&xorg;</application>
- uses <acronym>HAL</acronym> to autodetect keyboards and mice.
- The <filename role="package">sysutils/hal</filename> and
+ <para><application>&xorg;</application> uses
+ <acronym>HAL</acronym> to autodetect keyboards and mice. The
+ <filename role="package">sysutils/hal</filename> and
<filename role="package">devel/dbus</filename> ports are
- installed as dependencies of <filename
- role="package">x11/xorg</filename>, but must be enabled by
- the following entries in the
+ installed as dependencies of
+ <filename role="package">x11/xorg</filename>, but must be
+ enabled by the following entries in the
<filename>/etc/rc.conf</filename> file:</para>
<programlisting>hald_enable="YES"
@@ -437,9 +441,9 @@ dbus_enable="YES"</programlisting>
rebooting) before further <application>&xorg;</application>
configuration or use is attempted.</para>
- <para><application>&xorg;</application> can
- often work without any further configuration steps by
- simply typing at prompt:</para>
+ <para><application>&xorg;</application> can often work without
+ any further configuration steps by simply typing at
+ prompt:</para>
<screen>&prompt.user; <userinput>startx</userinput></screen>
@@ -465,16 +469,14 @@ dbus_enable="YES"</programlisting>
<screen>&prompt.root; <userinput>Xorg -configure</userinput></screen>
- <para>This will generate an
- X11 configuration skeleton file in the
- <filename>/root</filename> directory called
+ <para>This will generate an X11 configuration skeleton file in
+ the <filename>/root</filename> directory called
<filename>xorg.conf.new</filename> (whether you &man.su.1; or
do a direct login affects the inherited supervisor
- <envar>$HOME</envar> directory variable). The
- X11 program will attempt to probe
- the graphics hardware on the system and write a
- configuration file to load the proper drivers for the detected
- hardware on the target system.</para>
+ <envar>$HOME</envar> directory variable). The X11 program
+ will attempt to probe the graphics hardware on the system and
+ write a configuration file to load the proper drivers for the
+ detected hardware on the target system.</para>
<para>The next step is to test the existing
configuration to verify that <application>&xorg;</application>
@@ -504,9 +506,9 @@ dbus_enable="YES"</programlisting>
<keycap>Alt</keycap>
<keycap>Backspace</keycap>
</keycombo> key combination may also be used to break out of
- <application>&xorg;</application>. To enable it,
- you can either type the following
- command from any X terminal emulator:</para>
+ <application>&xorg;</application>. To enable it, you can
+ either type the following command from any X terminal
+ emulator:</para>
<screen>&prompt.user; <userinput>setxkbmap -option terminate:ctrl_alt_bksp</userinput></screen>
@@ -514,7 +516,7 @@ dbus_enable="YES"</programlisting>
<application>hald</application> called
<filename>x11-input.fdi</filename> and saved in the
<filename
- class="directory">/usr/local/etc/hal/fdi/policy</filename>
+ class="directory">/usr/local/etc/hal/fdi/policy</filename>
directory. This file should contain the following
lines:</para>
@@ -538,25 +540,25 @@ dbus_enable="YES"</programlisting>
<programlisting>Option "DontZap" "off"</programlisting>
</note>
- <para>If the mouse does not work, you will need to first
- configure it before proceeding. See <xref linkend="mouse"/>
- in the &os; install chapter. In recent
- <application>Xorg</application> versions,
- the <literal>InputDevice</literal> sections in
- <filename>xorg.conf</filename> are ignored in favor of the
- autodetected devices. To restore the old behavior, add the
- following line to the <literal>ServerLayout</literal> or
- <literal>ServerFlags</literal> section of this file:</para>
-
- <programlisting>Option "AutoAddDevices" "false"</programlisting>
-
- <para>Input devices may then be configured as in previous
- versions, along with any other options needed (e.g.,
- keyboard layout switching).</para>
+ <para>If the mouse does not work, you will need to first
+ configure it before proceeding. See <xref linkend="mouse"/>
+ in the &os; install chapter. In recent
+ <application>Xorg</application> versions,
+ the <literal>InputDevice</literal> sections in
+ <filename>xorg.conf</filename> are ignored in favor of the
+ autodetected devices. To restore the old behavior, add the
+ following line to the <literal>ServerLayout</literal> or
+ <literal>ServerFlags</literal> section of this file:</para>
+
+ <programlisting>Option "AutoAddDevices" "false"</programlisting>
+
+ <para>Input devices may then be configured as in previous
+ versions, along with any other options needed (e.g., keyboard
+ layout switching).</para>
<note>
- <para>As previously explained
- the <application>hald</application> daemon will, by default,
+ <para>As previously explained the
+ <application>hald</application> daemon will, by default,
automatically detect your keyboard. There are chances that
your keyboard layout or model will not be correct, desktop
environments like <application>GNOME</application>,
@@ -572,7 +574,7 @@ dbus_enable="YES"</programlisting>
configuration file for <application>hald</application>
called <filename>x11-input.fdi</filename> and saved in the
<filename
- class="directory">/usr/local/etc/hal/fdi/policy</filename>
+ class="directory">/usr/local/etc/hal/fdi/policy</filename>
directory. This file should contain the following
lines:</para>
@@ -605,13 +607,13 @@ dbus_enable="YES"</programlisting>
<indexterm><primary>X11 tuning</primary></indexterm>
- <para>The <filename>xorg.conf.new</filename>
- configuration file may now be tuned to taste. Open the
- file in a text editor such as &man.emacs.1; or &man.ee.1;.
- If the monitor is an older or unusual model that does not
- support autodetection of sync frequencies, those settings
- can be added to <filename>xorg.conf.new</filename>
- under the <literal>"Monitor"</literal> section:</para>
+ <para>The <filename>xorg.conf.new</filename> configuration file
+ may now be tuned to taste. Open the file in a text editor
+ such as &man.emacs.1; or &man.ee.1;. If the monitor is an
+ older or unusual model that does not support autodetection of
+ sync frequencies, those settings can be added to
+ <filename>xorg.conf.new</filename> under the
+ <literal>"Monitor"</literal> section:</para>
<programlisting>Section "Monitor"
Identifier "Monitor0"
@@ -622,9 +624,9 @@ dbus_enable="YES"</programlisting>
EndSection</programlisting>
<para>Most monitors support sync frequency autodetection,
- making manual entry of these values unnecessary. For the
- few monitors that do not support autodetection, avoid
- potential damage by only entering values provided by the
+ making manual entry of these values unnecessary. For the few
+ monitors that do not support autodetection, avoid potential
+ damage by only entering values provided by the
manufacturer.</para>
<para>X allows DPMS (Energy Star) features to be used with
@@ -640,9 +642,9 @@ EndSection</programlisting>
</indexterm>
<para>While the <filename>xorg.conf.new</filename>
- configuration file is still open in an editor, select
- the default resolution and color depth desired. This is
- defined in the <literal>"Screen"</literal> section:</para>
+ configuration file is still open in an editor, select the
+ default resolution and color depth desired. This is defined
+ in the <literal>"Screen"</literal> section:</para>
<programlisting>Section "Screen"
Identifier "Screen0"
@@ -656,45 +658,42 @@ EndSection</programlisting>
EndSubSection
EndSection</programlisting>
- <para>The <literal>DefaultDepth</literal> keyword describes
- the color depth to run at by default. This can be overridden
- with the <option>-depth</option> command line switch to
- &man.Xorg.1;.
- The <literal>Modes</literal> keyword
- describes the resolution to run at for the given color depth.
- Note that only VESA standard modes are supported as defined by
- the target system's graphics hardware.
- In the example above, the default color depth is twenty-four
- bits per pixel. At this color depth, the accepted
- resolution is 1024 by 768 pixels.</para>
+ <para>The <literal>DefaultDepth</literal> keyword describes the
+ color depth to run at by default. This can be overridden with
+ the <option>-depth</option> command line switch to
+ &man.Xorg.1;. The <literal>Modes</literal> keyword describes
+ the resolution to run at for the given color depth. Note that
+ only VESA standard modes are supported as defined by the
+ target system's graphics hardware. In the example above, the
+ default color depth is twenty-four bits per pixel. At this
+ color depth, the accepted resolution is 1024 by 768
+ pixels.</para>
<para>Finally, write the configuration file and test it using
the test mode given above.</para>
<note>
<para>One of the tools available to assist you during
- troubleshooting process are the X11 log files, which
- contain information on each device that the X11 server
- attaches to. <application>&xorg;</application> log file
- names are in the format of
- <filename>/var/log/Xorg.0.log</filename>. The exact name
- of the log can vary from <filename>Xorg.0.log</filename>
- to <filename>Xorg.8.log</filename> and so forth.</para>
+ troubleshooting process are the X11 log files, which contain
+ information on each device that the X11 server attaches to.
+ <application>&xorg;</application> log file names are in the
+ format of <filename>/var/log/Xorg.0.log</filename>. The
+ exact name of the log can vary from
+ <filename>Xorg.0.log</filename> to
+ <filename>Xorg.8.log</filename> and so forth.</para>
</note>
- <para>If all is well, the configuration
- file needs to be installed in a common location where
- &man.Xorg.1; can find it.
+ <para>If all is well, the configuration file needs to be
+ installed in a common location where &man.Xorg.1; can find it.
This is typically <filename>/etc/X11/xorg.conf</filename> or
<filename>/usr/local/etc/X11/xorg.conf</filename>.</para>
<screen>&prompt.root; <userinput>cp xorg.conf.new /etc/X11/xorg.conf</userinput></screen>
- <para>The X11 configuration process is now
- complete. <application>&xorg;</application> may be now
- started with the &man.startx.1; utility.
- The X11 server may also be started with the use of
- &man.xdm.1;.</para>
+ <para>The X11 configuration process is now complete.
+ <application>&xorg;</application> may be now started with the
+ &man.startx.1; utility. The X11 server may also be started
+ with the use of &man.xdm.1;.</para>
</sect2>
<sect2>
@@ -704,47 +703,62 @@ EndSection</programlisting>
<title>Configuration with &intel; <literal>i810</literal>
Graphics Chipsets</title>
- <indexterm><primary>Intel i810 graphic chipset</primary></indexterm>
+ <indexterm>
+ <primary>Intel i810 graphic chipset</primary>
+ </indexterm>
<para>Configuration with &intel; i810 integrated chipsets
- requires the <devicename>agpgart</devicename>
- AGP programming interface for X11
- to drive the card. See the &man.agp.4; driver manual page
- for more information.</para>
+ requires the <devicename>agpgart</devicename> AGP
+ programming interface for X11 to drive the card. See the
+ &man.agp.4; driver manual page for more information.</para>
<para>This will allow configuration of the hardware as any
other graphics board. Note on systems without the
&man.agp.4; driver compiled in the kernel, trying to load
- the module with &man.kldload.8; will not work. This
- driver has to be in the kernel at boot time through being
- compiled in or using
- <filename>/boot/loader.conf</filename>.</para>
+ the module with &man.kldload.8; will not work. This driver
+ has to be in the kernel at boot time through being compiled
+ in or using <filename>/boot/loader.conf</filename>.</para>
</sect3>
<sect3>
<title>Adding a Widescreen Flatpanel to the Mix</title>
- <indexterm><primary>widescreen flatpanel configuration</primary></indexterm>
+ <indexterm>
+ <primary>widescreen flatpanel configuration</primary>
+ </indexterm>
<para>This section assumes a bit of advanced configuration
knowledge. If attempts to use the standard configuration
tools above have not resulted in a working configuration,
- there is information enough in the log files to be of use
- in getting the setup working. Use of a text editor will
- be necessary.</para>
-
- <para>Current widescreen (WSXGA, WSXGA+, WUXGA, WXGA,
- WXGA+, et.al.) formats support 16:10 and 10:9 formats or
- aspect ratios that can be problematic. Examples of some
- common screen resolutions for 16:10 aspect ratios
- are:</para>
+ there is information enough in the log files to be of use in
+ getting the setup working. Use of a text editor will be
+ necessary.</para>
+
+ <para>Current widescreen (WSXGA, WSXGA+, WUXGA, WXGA, WXGA+,
+ et.al.) formats support 16:10 and 10:9 formats or aspect
+ ratios that can be problematic. Examples of some common
+ screen resolutions for 16:10 aspect ratios are:</para>
<itemizedlist>
- <listitem><para>2560x1600</para></listitem>
- <listitem><para>1920x1200</para></listitem>
- <listitem><para>1680x1050</para></listitem>
- <listitem><para>1440x900</para></listitem>
- <listitem><para>1280x800</para></listitem>
+ <listitem>
+ <para>2560x1600</para>
+ </listitem>
+
+ <listitem>
+ <para>1920x1200</para>
+ </listitem>
+
+ <listitem>
+ <para>1680x1050</para>
+ </listitem>
+
+ <listitem>
+ <para>1440x900</para>
+ </listitem>
+
+ <listitem>
+ <para>1280x800</para>
+ </listitem>
</itemizedlist>
<para>At some point, it will be as easy as adding one of these
@@ -764,17 +778,17 @@ EndSubSection
EndSection</programlisting>
<para><application>&xorg;</application> is smart enough to
- pull the resolution information from the widescreen via
- I2C/DDC information so it knows what the monitor can
- handle as far as frequencies and resolutions.</para>
+ pull the resolution information from the widescreen via
+ I2C/DDC information so it knows what the monitor can handle
+ as far as frequencies and resolutions.</para>
<para>If those <literal>ModeLines</literal> do not exist in
the drivers, one might need to give
<application>&xorg;</application> a little hint. Using
<filename>/var/log/Xorg.0.log</filename> one can extract
enough information to manually create a
- <literal>ModeLine</literal> that will work. Simply look
- for information resembling this:</para>
+ <literal>ModeLine</literal> that will work. Simply look for
+ information resembling this:</para>
<programlisting>(II) MGA(0): Supported additional Video Mode:
(II) MGA(0): clock: 146.2 MHz Image Size: 433 x 271 mm
@@ -789,8 +803,8 @@ EndSection</programlisting>
<programlisting>ModeLine <name> <clock> <4 horiz. timings> <4 vert. timings></programlisting>
<para>So that the <literal>ModeLine</literal> in
- <literal>Section "Monitor"</literal>
- for this example would look like this:</para>
+ <literal>Section "Monitor"</literal> for this example would
+ look like this:</para>
<programlisting>Section "Monitor"
Identifier "Monitor1"
@@ -819,41 +833,41 @@ EndSection</programlisting>
<title>Using Fonts in X11</title>
<sect2 id="type1">
- <title>Type1 Fonts</title>
+ <title>Type1 Fonts</title>
- <para>The default fonts that ship with X11 are less than ideal
- for typical desktop publishing applications. Large
- presentation fonts show up jagged and unprofessional looking,
- and small fonts are
- almost completely unintelligible. However, there are several
- free, high quality Type1 (&postscript;) fonts available which
- can be readily used with X11. For instance, the URW font
- collection (<filename
- role="package">x11-fonts/urwfonts</filename>) includes high
- quality versions of standard type1 fonts (<trademark
- class="registered">Times Roman</trademark>,
- <trademark class="registered">Helvetica</trademark>, <trademark
- class="registered">Palatino</trademark> and others). The
- Freefonts collection (<filename
- role="package">x11-fonts/freefonts</filename>) includes
- many more fonts, but most of them are intended for use in
- graphics software such as the <application>Gimp</application>,
- and are not complete enough to serve as screen fonts. In
- addition, X11 can be configured to use &truetype; fonts with
- a minimum of effort. For more details on this, see the
- &man.X.7; manual page or the <link linkend="truetype">section
- on &truetype; fonts</link>.</para>
+ <para>The default fonts that ship with X11 are less than ideal
+ for typical desktop publishing applications. Large
+ presentation fonts show up jagged and unprofessional looking,
+ and small fonts are almost completely unintelligible.
+ However, there are several free, high quality Type1
+ (&postscript;) fonts available which can be readily used with
+ X11. For instance, the URW font collection
+ (<filename role="package">x11-fonts/urwfonts</filename>)
+ includes high quality versions of standard type1 fonts
+ (<trademark class="registered">Times Roman</trademark>,
+ <trademark class="registered">Helvetica</trademark>,
+ <trademark class="registered">Palatino</trademark> and
+ others). The Freefonts collection
+ (<filename role="package">x11-fonts/freefonts</filename>)
+ includes many more fonts, but most of them are intended for
+ use in graphics software such as the
+ <application>Gimp</application>, and are not complete enough
+ to serve as screen fonts. In addition, X11 can be configured
+ to use &truetype; fonts with a minimum of effort. For more
+ details on this, see the &man.X.7; manual page or the
+ <link linkend="truetype">section on &truetype;
+ fonts</link>.</para>
- <para>To install the above Type1 font collections from the
- Ports Collection, run the following commands:</para>
+ <para>To install the above Type1 font collections from the
+ Ports Collection, run the following commands:</para>
- <screen>&prompt.root; <userinput>cd /usr/ports/x11-fonts/urwfonts</userinput>
+ <screen>&prompt.root; <userinput>cd /usr/ports/x11-fonts/urwfonts</userinput>
&prompt.root; <userinput>make install clean</userinput></screen>
- <para>And likewise with the freefont or other collections. To
- have the X server detect these fonts, add an appropriate line
- to the X server configuration file
- (<filename>/etc/X11/xorg.conf</filename>), which reads:</para>
+ <para>And likewise with the freefont or other collections. To
+ have the X server detect these fonts, add an appropriate line
+ to the X server configuration file
+ (<filename>/etc/X11/xorg.conf</filename>), which reads:</para>
<programlisting>FontPath "/usr/local/lib/X11/fonts/URW/"</programlisting>
@@ -871,55 +885,58 @@ EndSection</programlisting>
graphical login manager like <application>XDM</application>).
A third way is to use the new
<filename>/usr/local/etc/fonts/local.conf</filename> file: see
- the section on <link
- linkend="antialias">anti-aliasing</link>.</para>
+ the section on
+ <link linkend="antialias">anti-aliasing</link>.</para>
</sect2>
<sect2 id="truetype">
- <title>&truetype; Fonts</title>
+ <title>&truetype; Fonts</title>
- <indexterm><primary>TrueType Fonts</primary></indexterm>
- <indexterm><primary>fonts</primary>
- <secondary>TrueType</secondary>
- </indexterm>
-
- <para><application>&xorg;</application> has built in support
- for rendering &truetype; fonts. There are two different
- modules that can enable this functionality. The freetype
- module is used in this example because it is more consistent
- with the other font rendering back-ends. To enable the
- freetype module just add the following line to the
- <literal>"Module"</literal> section of the
- <filename>/etc/X11/xorg.conf</filename> file.</para>
-
- <programlisting>Load "freetype"</programlisting>
-
- <para>Now make a directory for the &truetype; fonts (for
- example,
- <filename>/usr/local/lib/X11/fonts/TrueType</filename>)
- and copy all of the &truetype; fonts into this directory.
- Keep in mind that &truetype; fonts cannot be directly taken
- from a &macintosh;; they must be in &unix;/&ms-dos;/&windows;
- format for use by X11. Once the files have been copied into
- this directory, use <application>ttmkfdir</application> to
- create a <filename>fonts.dir</filename> file, so that the X
- font renderer knows that these new files have been installed.
- <command>ttmkfdir</command> is available from the FreeBSD
- Ports Collection as
- <filename role="package">x11-fonts/ttmkfdir</filename>.</para>
+ <indexterm>
+ <primary>TrueType Fonts</primary>
+ </indexterm>
+ <indexterm>
+ <primary>fonts</primary>
+ <secondary>TrueType</secondary>
+ </indexterm>
+
+ <para><application>&xorg;</application> has built in support for
+ rendering &truetype; fonts. There are two different modules
+ that can enable this functionality. The freetype module is
+ used in this example because it is more consistent with the
+ other font rendering back-ends. To enable the freetype module
+ just add the following line to the <literal>"Module"</literal>
+ section of the <filename>/etc/X11/xorg.conf</filename>
+ file.</para>
+
+ <programlisting>Load "freetype"</programlisting>
+
+ <para>Now make a directory for the &truetype; fonts (for
+ example,
+ <filename>/usr/local/lib/X11/fonts/TrueType</filename>) and
+ copy all of the &truetype; fonts into this directory. Keep in
+ mind that &truetype; fonts cannot be directly taken from a
+ &macintosh;; they must be in &unix;/&ms-dos;/&windows; format
+ for use by X11. Once the files have been copied into this
+ directory, use <application>ttmkfdir</application> to create a
+ <filename>fonts.dir</filename> file, so that the X font
+ renderer knows that these new files have been installed.
+ <command>ttmkfdir</command> is available from the FreeBSD
+ Ports Collection as
+ <filename role="package">x11-fonts/ttmkfdir</filename>.</para>
- <screen>&prompt.root; <userinput>cd /usr/local/lib/X11/fonts/TrueType</userinput>
+ <screen>&prompt.root; <userinput>cd /usr/local/lib/X11/fonts/TrueType</userinput>
&prompt.root; <userinput>ttmkfdir -o fonts.dir</userinput></screen>
- <para>Now add the &truetype; directory to the font
- path. This is just the same as described above for <link
- linkend="type1">Type1</link> fonts, that is, use</para>
+ <para>Now add the &truetype; directory to the font path. This
+ is just the same as described above for
+ <link linkend="type1">Type1</link> fonts, that is, use</para>
- <screen>&prompt.user; <userinput>xset fp+ /usr/local/lib/X11/fonts/TrueType</userinput>
+ <screen>&prompt.user; <userinput>xset fp+ /usr/local/lib/X11/fonts/TrueType</userinput>
&prompt.user; <userinput>xset fp rehash</userinput></screen>
- <para>or add a <literal>FontPath</literal> line to the
- <filename>xorg.conf</filename> file.</para>
+ <para>or add a <literal>FontPath</literal> line to the
+ <filename>xorg.conf</filename> file.</para>
<para>That's it. Now <application>Gimp</application>,
<application>Apache OpenOffice</application>, and all of the
@@ -931,75 +948,79 @@ EndSection</programlisting>
</sect2>
<sect2 id="antialias">
- <sect2info>
- <authorgroup>
- <author>
- <firstname>Joe Marcus</firstname>
- <surname>Clarke</surname>
- <contrib>Updated by </contrib>
- <!-- May 2003 -->
- </author>
- </authorgroup>
- </sect2info>
- <title>Anti-Aliased Fonts</title>
+ <sect2info>
+ <authorgroup>
+ <author>
+ <firstname>Joe Marcus</firstname>
+ <surname>Clarke</surname>
+ <contrib>Updated by </contrib>
+ <!-- May 2003 -->
+ </author>
+ </authorgroup>
+ </sect2info>
+ <title>Anti-Aliased Fonts</title>
+
+ <indexterm>
+ <primary>anti-aliased fonts</primary>
+ </indexterm>
+ <indexterm>
+ <primary>fonts</primary>
+ <secondary>anti-aliased</secondary>
+ </indexterm>
- <indexterm><primary>anti-aliased fonts</primary></indexterm>
- <indexterm><primary>fonts</primary>
- <secondary>anti-aliased</secondary></indexterm>
-
- <para>All fonts in X11 that are found
- in <filename>/usr/local/lib/X11/fonts/</filename> and
- <filename>~/.fonts/</filename> are automatically
- made available for anti-aliasing to Xft-aware applications.
- Most recent applications are Xft-aware, including
- <application>KDE</application>,
- <application>GNOME</application>, and
- <application>Firefox</application>.</para>
-
- <para>In order to control which fonts are anti-aliased, or to
- configure anti-aliasing properties, create (or edit, if it
- already exists) the file
- <filename>/usr/local/etc/fonts/local.conf</filename>. Several
- advanced features of the Xft font system can be tuned using
- this file; this section describes only some simple
- possibilities. For more details, please see
- &man.fonts-conf.5;.</para>
-
- <indexterm><primary>XML</primary></indexterm>
-
- <para>This file must be in XML format. Pay careful attention
- to case, and make sure all tags are properly closed. The
- file begins with the usual XML header followed by a DOCTYPE
- definition, and then the <literal><fontconfig></literal>
- tag:</para>
+ <para>All fonts in X11 that are found in
+ <filename>/usr/local/lib/X11/fonts/</filename> and
+ <filename>~/.fonts/</filename> are automatically made
+ available for anti-aliasing to Xft-aware applications. Most
+ recent applications are Xft-aware, including
+ <application>KDE</application>,
+ <application>GNOME</application>, and
+ <application>Firefox</application>.</para>
+
+ <para>In order to control which fonts are anti-aliased, or to
+ configure anti-aliasing properties, create (or edit, if it
+ already exists) the file
+ <filename>/usr/local/etc/fonts/local.conf</filename>. Several
+ advanced features of the Xft font system can be tuned using
+ this file; this section describes only some simple
+ possibilities. For more details, please see
+ &man.fonts-conf.5;.</para>
+
+ <indexterm><primary>XML</primary></indexterm>
+
+ <para>This file must be in XML format. Pay careful attention to
+ case, and make sure all tags are properly closed. The file
+ begins with the usual XML header followed by a DOCTYPE
+ definition, and then the <literal><fontconfig></literal>
+ tag:</para>
- <programlisting>
+ <programlisting>
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig></programlisting>
- <para>As previously stated, all fonts in
- <filename>/usr/local/lib/X11/fonts/</filename> as well as
- <filename>~/.fonts/</filename> are already made available to
- Xft-aware applications. If you wish to add another directory
- outside of these two directory trees, add a line similar to the
- following to
- <filename>/usr/local/etc/fonts/local.conf</filename>:</para>
-
- <programlisting><dir>/path/to/my/fonts</dir></programlisting>
-
- <para>After adding new fonts, and especially new font directories,
- you should run the following command to rebuild the font
- caches:</para>
-
- <screen>&prompt.root; <userinput>fc-cache -f</userinput></screen>
-
- <para>Anti-aliasing makes borders slightly fuzzy, which makes
- very small text more readable and removes
- <quote>staircases</quote> from large text, but can cause
- eyestrain if applied to normal text. To exclude font sizes
- smaller than 14 point from anti-aliasing, include these
- lines:</para>
+ <para>As previously stated, all fonts in
+ <filename>/usr/local/lib/X11/fonts/</filename> as well as
+ <filename>~/.fonts/</filename> are already made available to
+ Xft-aware applications. If you wish to add another directory
+ outside of these two directory trees, add a line similar to
+ the following to
+ <filename>/usr/local/etc/fonts/local.conf</filename>:</para>
+
+ <programlisting><dir>/path/to/my/fonts</dir></programlisting>
+
+ <para>After adding new fonts, and especially new font
+ directories, you should run the following command to rebuild
+ the font caches:</para>
+
+ <screen>&prompt.root; <userinput>fc-cache -f</userinput></screen>
+
+ <para>Anti-aliasing makes borders slightly fuzzy, which makes
+ very small text more readable and removes
+ <quote>staircases</quote> from large text, but can cause
+ eyestrain if applied to normal text. To exclude font sizes
+ smaller than 14 point from anti-aliasing, include these
+ lines:</para>
<programlisting> <match target="font">
<test name="size" compare="less">
@@ -1018,16 +1039,18 @@ EndSection</programlisting>
</edit>
</match></programlisting>
- <indexterm><primary>fonts</primary>
- <secondary>spacing</secondary></indexterm>
+ <indexterm>
+ <primary>fonts</primary>
+ <secondary>spacing</secondary>
+ </indexterm>
- <para>Spacing for some monospaced fonts may also be inappropriate
- with anti-aliasing. This seems to be an issue with
- <application>KDE</application>, in particular. One possible
- fix for this is to force the spacing for such fonts to be 100.
- Add the following lines:</para>
+ <para>Spacing for some monospaced fonts may also be
+ inappropriate with anti-aliasing. This seems to be an issue
+ with <application>KDE</application>, in particular. One
+ possible fix for this is to force the spacing for such fonts
+ to be 100. Add the following lines:</para>
- <programlisting> <match target="pattern" name="family">
+ <programlisting> <match target="pattern" name="family">
<test qual="any" name="family">
<string>fixed</string>
</test>
@@ -1059,9 +1082,8 @@ EndSection</programlisting>
<para>Certain fonts, such as Helvetica, may have a problem when
anti-aliased. Usually this manifests itself as a font that
seems cut in half vertically. At worst, it may cause
- applications to
- crash. To avoid this, consider adding the following to
- <filename>local.conf</filename>:</para>
+ applications to crash. To avoid this, consider adding the
+ following to <filename>local.conf</filename>:</para>
<programlisting> <match target="pattern" name="family">
<test qual="any" name="family">
@@ -1077,24 +1099,24 @@ EndSection</programlisting>
with the <literal></fontconfig></literal> tag. Not
doing this will cause your changes to be ignored.</para>
- <para>Finally, users can add their own settings via their
- personal <filename>.fonts.conf</filename> files. To do
- this, each user should simply create a
- <filename>~/.fonts.conf</filename>. This file must also be
- in XML format.</para>
-
- <indexterm><primary>LCD screen</primary></indexterm>
- <indexterm><primary>Fonts</primary>
- <secondary>LCD screen</secondary></indexterm>
-
- <para>One last point: with an LCD screen, sub-pixel sampling
- may be desired. This basically treats the (horizontally
- separated) red, green and blue components separately to
- improve the horizontal resolution; the results can be
- dramatic. To enable this, add the line somewhere in the
- <filename>local.conf</filename> file:</para>
+ <para>Finally, users can add their own settings via their
+ personal <filename>.fonts.conf</filename> files. To do this,
+ each user should simply create a
+ <filename>~/.fonts.conf</filename>. This file must also be in
+ XML format.</para>
+
+ <indexterm><primary>LCD screen</primary></indexterm>
+ <indexterm><primary>Fonts</primary>
+ <secondary>LCD screen</secondary></indexterm>
+
+ <para>One last point: with an LCD screen, sub-pixel sampling may
+ be desired. This basically treats the (horizontally
+ separated) red, green and blue components separately to
+ improve the horizontal resolution; the results can be
+ dramatic. To enable this, add the line somewhere in the
+ <filename>local.conf</filename> file:</para>
- <programlisting>
+ <programlisting>
<match target="font">
<test qual="all" name="rgba">
<const>unknown</const>
@@ -1104,13 +1126,13 @@ EndSection</programlisting>
</edit>
</match></programlisting>
- <note>
+ <note>
<para>Depending on the sort of display,
<literal>rgb</literal> may need to be changed to
<literal>bgr</literal>, <literal>vrgb</literal> or
<literal>vbgr</literal>: experiment and see which works
best.</para>
- </note>
+ </note>
</sect2>
</sect1>
@@ -1125,8 +1147,8 @@ EndSection</programlisting>
</authorgroup>
</sect1info>
<title>The X Display Manager</title>
- <sect2>
+ <sect2>
<title>Overview</title>
<indexterm><primary>X Display Manager</primary></indexterm>
@@ -1143,17 +1165,16 @@ EndSection</programlisting>
and entering authorization information such as a login and
password combination.</para>
- <para>Think of <application>XDM</application> as
- providing the same functionality to the user as the
- &man.getty.8; utility (see <xref linkend="term-config"/> for
- details). That is, it performs system logins to the display
- being connected to and then runs a session manager on
- behalf of the user (usually an X window manager).
- <application>XDM</application> then waits for this program to
- exit, signaling that the user is done and should be logged out
- of the display. At this point, <application>XDM</application>
- can display the login and display chooser screens for the next
- user to login.</para>
+ <para>Think of <application>XDM</application> as providing the
+ same functionality to the user as the &man.getty.8; utility
+ (see <xref linkend="term-config"/> for details). That is, it
+ performs system logins to the display being connected to and
+ then runs a session manager on behalf of the user (usually an
+ X window manager). <application>XDM</application> then waits
+ for this program to exit, signaling that the user is done and
+ should be logged out of the display. At this point,
+ <application>XDM</application> can display the login and
+ display chooser screens for the next user to login.</para>
</sect2>
<sect2>
@@ -1167,12 +1188,12 @@ EndSection</programlisting>
found in <filename>/usr/local/bin/xdm</filename>. This
program can be run at any time as <username>root</username>
and it will start managing the X display on the local machine.
- If <application>XDM</application> is to be run every
- time the machine boots up, a convenient way to do this is by
*** DIFF OUTPUT TRUNCATED AT 1000 LINES ***