- Refresh sections on Anti-aliased fonts a bit:

* Remove description of quirks of ancient X, KDE and GNOME versions
  * Remove mentions of Mozilla, it's dead
  * No need to mention bitstream-vera package, these days it's part of default
    xorg meta-port

en_US.ISO8859-1/books/handbook/x11/chapter.sgml

@@ -932,23 +932,12 @@ EndSection</programlisting>
     <indexterm><primary>fonts</primary>
       <secondary>anti-aliased</secondary></indexterm>
 
-    <para>Anti-aliasing has been available in X11 since
-      <application>&xfree86;</application> 4.0.2.  However, font
-      configuration was cumbersome before the introduction of
-      <application>&xfree86;</application> 4.3.0.
-      Beginning with
-      <application>&xfree86;</application> 4.3.0, all fonts in X11
-      that are found
+    <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.  Not
-      all applications are Xft-aware, but many have received Xft support.
-      Examples of Xft-aware applications include Qt 2.3 and higher (the 
-      toolkit for the <application>KDE</application> desktop), 
-      GTK+ 2.0 and higher (the toolkit for the 
-      <application>GNOME</application> desktop), and 
-      <application>Mozilla</application> 1.2 and higher.
-    </para>
+      made available for anti-aliasing to Xft-aware applications.
+      Most recent applications are Xft-aware, including KDE, GNOME, and
+      Firefox.</para>
 
     <para>In order to control which fonts are anti-aliased, or to
       configure anti-aliasing properties, create (or edit, if it
@@ -1052,7 +1041,7 @@ 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 such as <application>Mozilla</application> to
+	applications to
 	crash.  To avoid this, consider adding the following to
 	<filename>local.conf</filename>:</para>
 
@@ -1070,13 +1059,6 @@ EndSection</programlisting>
         with the <literal>&lt;/fontconfig&gt;</literal> tag.  Not doing this will cause
         your changes to be ignored.</para>
 
-       <para>The default font set that comes with 
-	 X11 is not very
-         desirable when it comes to anti-aliasing.  A much better
-	 set of default fonts can be found in the 
-	 <filename role="package">x11-fonts/bitstream-vera</filename>
-	 port.</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 
@@ -1107,25 +1089,6 @@ EndSection</programlisting>
 	 <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>
-
-       <indexterm>
-	 <primary>Mozilla</primary>
-         <secondary>disabling anti-aliased fonts</secondary>
-       </indexterm>
-
-       <para>Anti-aliasing should be enabled the next time the X
-         server is started.  However, programs must know how to take
-         advantage of it.  At present, the Qt toolkit does,
-         so the entire <application>KDE</application> environment can
-         use anti-aliased fonts.
-         GTK+ and 
-         <application>GNOME</application> can also be made to use 
-         anti-aliasing via the <quote>Font</quote> capplet (see <xref
-         linkend="x11-wm-gnome-antialias"> for details).  By default,
-         <application>Mozilla</application> 1.2 and greater will 
-         automatically use anti-aliasing. To disable this, rebuild 
-         <application>Mozilla</application> with the
-         <makevar>-DWITHOUT_XFT</makevar> flag.</para>
     </sect2>
   </sect1>