release-notes/FC4 xorg.xml,1.4,1.5

Karsten Wade (kwade) fedora-docs-commits at redhat.com
Mon May 30 17:52:20 UTC 2005


Author: kwade

Update of /cvs/docs/release-notes/FC4
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv25510

Modified Files:
	xorg.xml 
Log Message:
Clean up to make it look good without all the bullets around it.  Hoping to use nicer formatting in the future.


Index: xorg.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/xorg.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- xorg.xml	30 May 2005 17:40:09 -0000	1.4
+++ xorg.xml	30 May 2005 17:52:18 -0000	1.5
@@ -1,183 +1,206 @@
 <section id="sn-xwindows">
- <title>X Window System (Graphics)</title>
-
-      <para>This section contains information related to the X Window System
-        implementation provided with &DISTRO;.</para>
-
-      <section id="sn-xwindows-xorg">
-        <title><filename>xorg-x11</filename></title>
-
-        
-          
-            <para>Users new to the X.org X11 implementation should take note of
-              a few differences between it and the XFree86.org X11
-              implementation which shipped in previous &RH; operating systems.
-              In particular, the names of some files have changed:</para>
-
-            <para>X Server Binary:</para>
-
-            <itemizedlist>
-              <listitem>
-                <para>XFree86 X11: <filename>XFree86</filename></para>
-              </listitem>
-
-              <listitem>
-                <para>X.org X11: <filename>Xorg</filename></para>
-              </listitem>
-            </itemizedlist>
-
-            <para>X Server Configuration File:</para>
-
-            <itemizedlist>
-              <listitem>
-                <para>XFree86 X11:
-                  <filename>/etc/X11/XF86Config</filename></para>
-              </listitem>
-
-              <listitem>
-                <para>X.org X11: <filename>/etc/X11/xorg.conf</filename></para>
-              </listitem>
-            </itemizedlist>
-
-            <para>X Server Log File:</para>
-
-            <itemizedlist>
-              <listitem>
-                <para>XFree86 X11:
-                  <filename>/var/log/XFree86.<replaceable>$DISPLAY</replaceable>.log</filename></para>
-              </listitem>
-
-              <listitem>
-                <para>X.org X11:
-                  <filename>/var/log/Xorg.<replaceable>$DISPLAY</replaceable>.log</filename></para>
-              </listitem>
-            </itemizedlist>
-
-            <para>When configuring or troubleshooting your X server
-              configuration, be sure that you are using the correct
-              files.</para>
-          
-
-          
-            <para>There has been some confusion regarding font-related issues
-              under the X Window System in recent versions of &DISTRO; (and
-              versions of &RHL; before it.)  At the present time, there are two
-              font subsystems, each with different characteristics:</para>
-
-            <para>- The original (15+ year old) subsystem is referred to as the
-              "core X font subsystem".  Fonts rendered by this subsystem are not
-              anti-aliased, are handled by the X server, and have names
-              like:</para>
-
-            <para>-misc-fixed-medium-r-normal--10-100-75-75-c-60-iso8859-1</para>
-
-            <para>The newer font subsystem is known as "fontconfig", and allows
-              applications direct access to the font files.  Fontconfig is often
-              used along with the Xft library, which allows applications to
-              render fontconfig fonts to the screen with antialiasing.
-              Fontconfig uses more human-friendly names such as:</para>
-
-            <para>Luxi Sans-10</para>
-
-            <para>Over time, fontconfig and Xft will replace the core X font
-              subsystem.  At the present time, applications using the Qt 3 or
-              GTK 2 toolkits (which would include KDE and GNOME applications)
-              use the fontconfig and Xft font subsystem; most everything else
-              uses the core X fonts.</para>
-
-            <para>In the future, &DISTRO; may support only fontconfig/Xft in
-              place of the XFS font server as the default local font access
-              method.</para>
-
-            <para>NOTE: An exception to the font subsystem usage outlined above
-              is OpenOffice.org (which uses its own font rendering
-              technology).</para>
-
-            <para>If you wish to add new fonts to your &DISTRO; &DISTROVER;
-              system, you must be aware that the steps necessary depend on which
-              font subsystem is to use the new fonts.  For the core X font
-              subsystem, you must:</para>
-
-            <para>1. Create the <filename>/usr/share/fonts/local/</filename>
-              directory (if it doesn't already exist):</para>
-
-            <para><command>mkdir /usr/share/fonts/local/</command></para>
-
-            <para>2. Copy the new font file into
-              <filename>/usr/share/fonts/local/</filename></para>
-
-            <para>3. Update the font information by issuing the following
+  <title>X Window System (Graphics)</title>
+  <para>
+    This section contains information related to the X Window System
+    implementation provided with &DISTRO;.
+  </para>
+  <section id="sn-xwindows-xorg">
+    <title><filename>xorg-x11</filename></title>
+    <para>
+      Users new to the X.org X11 implementation should take note of
+      a few differences between it and the XFree86.org X11
+      implementation which shipped in previous &RH; operating systems.
+      In particular, the names of some files have changed:
+    </para>
+    <para>
+      X Server Binary:
+    </para>
+    <itemizedlist>
+      <listitem>
+	<para>XFree86 X11: <filename>XFree86</filename></para>
+      </listitem>
+      <listitem>
+	<para>X.org X11: <filename>Xorg</filename></para>
+      </listitem>
+    </itemizedlist>
+    <para>
+      X Server Configuration File:
+    </para>
+    <itemizedlist>
+      <listitem>
+	<para>XFree86 X11:
+	  <filename>/etc/X11/XF86Config</filename></para>
+      </listitem>
+      <listitem>
+	<para>X.org X11: <filename>/etc/X11/xorg.conf</filename></para>
+      </listitem>
+    </itemizedlist>
+    <para>
+      X Server Log File:
+    </para>
+    <itemizedlist>
+      <listitem>
+	<para>XFree86 X11:
+	  <filename>/var/log/XFree86.<replaceable>$DISPLAY</replaceable>.log</filename></para>
+      </listitem>
+      <listitem>
+	<para>X.org X11:
+	  <filename>/var/log/Xorg.<replaceable>$DISPLAY</replaceable>.log</filename></para>
+      </listitem>
+    </itemizedlist>
+    <para>
+      When configuring or troubleshooting your X server
+      configuration, be sure that you are using the correct
+      files.
+    </para>
+    <para>
+      There has been some confusion regarding font-related issues
+      under the X Window System in recent versions of &DISTRO; (and
+      versions of &RHL; before it.)  At the present time, there are two
+      font subsystems, each with different characteristics:
+    </para>
+    <itemizedlist>
+      <listitem>
+	<para>The original (15+ year old) subsystem is referred to as the
+	  "core X font subsystem".  Fonts rendered by this subsystem are not
+	  anti-aliased, are handled by the X server, and have names
+	  like: <computeroutput>-misc-fixed-medium-r-normal--10-100-75-75-c-60-iso8859-1</computeroutput>
+	</para>
+      </listitem>
+      <listitem>
+	<para>
+	  The newer font subsystem is known as "fontconfig", and allows
+	  applications direct access to the font files.  Fontconfig is
+	  often used along with the Xft library, which allows
+	  applications to render fontconfig fonts to the screen with
+	  antialiasing. Fontconfig uses more human-friendly names such
+	  as:  <computeroutput>Luxi Sans-10</computeroutput>
+	</para>
+      </listitem>
+    </itemizedlist>
+    <para>
+      Over time, fontconfig and Xft will replace the core X font
+      subsystem.  At the present time, applications using the Qt 3 or
+      GTK 2 toolkits (which would include KDE and GNOME applications)
+      use the fontconfig and Xft font subsystem; most everything else
+      uses the core X fonts.
+    </para>
+    <para>
+      In the future, &FC; may support only fontconfig/Xft in
+      place of the XFS font server as the default local font access
+      method.
+    </para>
+    <note>
+      <title>Note</title>
+      <para>
+	An exception to the font subsystem usage outlined above
+	is OpenOffice.org (which uses its own font rendering
+	technology).
+      </para>
+    </note>
+    <para>
+      If you wish to add new fonts to your &DISTRO; &DISTROVER;
+      system, you must be aware that the steps necessary depend on which
+      font subsystem is to use the new fonts.  For the core X font
+      subsystem, you must:
+    </para>
+
+    <procedure>
+      <step>
+	<para>
+	  Create the <filename>/usr/share/fonts/local/</filename>
+	  directory (if it doesn't already exist):
+	</para>
+<screen>
+<command>mkdir /usr/share/fonts/local/</command>
+</screen>
+      </step>
+      <step>
+	<para>
+	  Copy the new font file into
+	  <filename>/usr/share/fonts/local/</filename>
+	</para>
+      </step>
+      <step>
+	<para>
+	  Update the font information by issuing the following
               commands (note that, due to formatting restrictions, the following
               commands may appear on more than one line; in use, each command
-              should be entered on a single line):</para>
-
-            <para><command>ttmkfdir -d /usr/share/fonts/local/ -o
-                /usr/share/fonts/local/fonts.scale</command></para>
-
-            <para><command>mkfontdir /usr/share/fonts/local/</command></para>
-
-            <para>4. If you had to create
-              <filename>/usr/share/fonts/local/</filename>, you must then add it
-              to the X font server (xfs) path:</para>
-
-            <para><command>chkfontpath --add
-                /usr/share/fonts/local/</command></para>
-
-            <para>Adding new fonts to the fontconfig font subsystem is more
-              straightforward; the new font file only needs to be copied into
-              the <filename>/usr/share/fonts/</filename> directory (individual
-              users can modify their personal font configuration by copying the
-              font file into the <filename>~/.fonts/</filename>
-              directory).</para>
-
-            <para>After the new font has been copied, use
-              <command>fc-cache</command> to update the font information
-              cache:</para>
-
-            <para><command>fc-cache
-                <replaceable><directory></replaceable></command></para>
-
-            <para>(Where
-              <command><replaceable><directory></replaceable></command>
-              would be either the <filename>/usr/share/fonts/</filename> or
-              <filename>~/.fonts/</filename> directories.)</para>
-
-            <para>Individual users may also install fonts graphically, by
-              browsing <command>fonts:///</command> in
-              <application>Nautilus</application>, and dragging the new font
-              files there.</para>
-
-            <para>NOTE: If the font filename ends with
-              "<filename>.gz</filename>", it has been compressed with
-              <command>gzip</command>, and must be decompressed (with the
-              <command>gunzip</command> command) before the fontconfig font
-              subsystem can use the font.</para>
-          
-
-          
-            <para>Due to the transition to the new font system based on
-              fontconfig/Xft, GTK+ 1.2 applications are not affected by any
-              changes made via the <guilabel>Font Preferences</guilabel> dialog.
-              For these applications, a font can be configured by adding the
-              following lines to the file
-              <filename>~/.gtkrc.mine</filename>:</para>
-
-            <para><command>style "user-font" {</command></para>
-            <para><command>fontset =
-                "<replaceable><font-specification></replaceable>"</command></para>
-            <para><command>}</command></para>
-            <para><computeroutput> </computeroutput></para>
-            <para><computeroutput>widget_class "*" style "user-font"</computeroutput></para>
-
-            <para>(Where
-              <command><replaceable><font-specification></replaceable></command>
-              represents a font specification in the style used by traditional X
-              applications, such as
-              "<computeroutput>-adobe-helvetica-medium-r-normal--*-120-*-*-*-*-*-*</computeroutput>".)</para>
-          
-        
-      </section>
-    </section>
+              should be entered on a single line):
+	</para>
+<screen>
+<command>ttmkfdir -d /usr/share/fonts/local/ -o /usr/share/fonts/local/fonts.scale</command>
+<command>mkfontdir /usr/share/fonts/local/</command>
+</screen>
+      </step>
+      <step>
+	<para>
+	  If you had to create
+	  <filename>/usr/share/fonts/local/</filename>, you must then
+	  add it to the X font server (xfs) path:
+	</para>
+<screen>
+<command>chkfontpath --add /usr/share/fonts/local/</command>
+</screen>
+      </step>
+    </procedure>
+    <para>
+      Adding new fonts to the fontconfig font subsystem is more
+      straightforward; the new font file only needs to be copied into
+      the <filename>/usr/share/fonts/</filename> directory (individual
+      users can modify their personal font configuration by copying the
+      font file into the <filename>~/.fonts/</filename> directory).
+    </para>
+    <para>
+      After the new font has been copied, use
+      <command>fc-cache</command> to update the font information cache:
+    </para>
+<screen>
+<command>fc-cache <replaceable><directory></replaceable></command>
+</screen>
+    <para>
+      (Where
+      <command><replaceable><directory></replaceable></command>
+      would be either the <filename>/usr/share/fonts/</filename> or
+      <filename>~/.fonts/</filename> directories.)
+    </para>
+    <para>
+      Individual users may also install fonts graphically, by browsing
+      <command>fonts:///</command> in
+      <application>Nautilus</application>, and dragging the new font
+      files there.
+    </para>
+    <note>
+      <title>Note</title>
+      <para>
+	If the font filename ends with "<filename>.gz</filename>", it
+	has been compressed with <command>gzip</command>, and must be
+	decompressed (with the <command>gunzip</command> command) before
+	the fontconfig font subsystem can use the font.
+      </para>
+    </note>      
+    <para>
+      Due to the transition to the new font system based on
+      fontconfig/Xft, GTK+ 1.2 applications are not affected by any
+      changes made via the <guilabel>Font Preferences</guilabel> dialog.
+      For these applications, a font can be configured by adding the
+      following lines to the file <filename>~/.gtkrc.mine</filename>:
+    </para>
+<screen>    
+<computeroutput>style "user-font" {
+fontset = "<replaceable><font-specification></replaceable>"
+}
+widget_class "*" style "user-font"</computeroutput>
+</screen>
+    <para>
+      (Where
+      <command><replaceable><font-specification></replaceable></command> 
+      represents a font specification in the style used by traditional X
+      applications, such as
+      "<computeroutput>-adobe-helvetica-medium-r-normal--*-120-*-*-*-*-*-*</computeroutput>".)
+    </para>
+  </section>
+</section>
 
 <!--
 Local variables:




More information about the Fedora-docs-commits mailing list