diff --git a/en_US.ISO8859-1/books/fdp-primer/book.sgml b/en_US.ISO8859-1/books/fdp-primer/book.sgml
index 26485ba9f9..d3cb1e1cb1 100644
--- a/en_US.ISO8859-1/books/fdp-primer/book.sgml
+++ b/en_US.ISO8859-1/books/fdp-primer/book.sgml
@@ -1,271 +1,273 @@
 <!-- Copyright (c) 1998, 1999 Nik Clayton, All rights reserved.
 
      Redistribution and use in source (SGML DocBook) and 'compiled' forms
      (SGML, HTML, PDF, PostScript, RTF and so forth) with or without
      modification, are permitted provided that the following conditions
      are met:
 
       1. Redistributions of source code (SGML DocBook) must retain the above
          copyright notice, this list of conditions and the following
          disclaimer as the first lines of this file unmodified.
 
       2. Redistributions in compiled form (transformed to other DTDs,
          converted to PDF, PostScript, RTF and other formats) must reproduce
          the above copyright notice, this list of conditions and the
          following disclaimer in the documentation and/or other materials
          provided with the distribution.
 
      THIS DOCUMENTATION IS PROVIDED BY NIK CLAYTON "AS IS" AND ANY EXPRESS OR
      IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
      OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
      DISCLAIMED. IN NO EVENT SHALL NIK CLAYTON BE LIABLE FOR ANY DIRECT,
      INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
      (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
      SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
      HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
      STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
      ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE
      POSSIBILITY OF SUCH DAMAGE.
 
      $FreeBSD$
 -->
 
 <!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
 
 <!ENTITY % bookinfo PUBLIC "-//FreeBSD//ENTITIES DocBook BookInfo Entities//EN">
 %bookinfo;
+<!ENTITY % freebsd PUBLIC "-//FreeBSD//ENTITIES DocBook Miscellaneous FreeBSD Entities//EN">
+%freebsd;
 <!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN">
 %authors;
 <!ENTITY % teams PUBLIC "-//FreeBSD//ENTITIES DocBook Team Entities//EN">
 %teams;
 <!ENTITY % mailing-lists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN">
 %mailing-lists;
 <!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
 %man;
 <!ENTITY % urls PUBLIC "-//FreeBSD//ENTITIES DocBook URL Entities//EN">
 %urls;
 
 <!ENTITY % chapters SYSTEM "chapters.ent"> %chapters;
 <!ENTITY % not.published "INCLUDE">
 <!-- ENTITY index SYSTEM "index.sgml" -->
 ]>
 
 <book>
   <bookinfo>
     <title>FreeBSD Documentation Project Primer for New Contributors</title>
    
     <corpauthor>The FreeBSD Documentation Project</corpauthor>
  
     <copyright>
       <year>1998</year>
       <year>1999</year>
       <year>2000</year>
       <year>2001</year>
       <year>2002</year>
       <year>2003</year>
       <year>2004</year>
       <holder role="mailto:doceng@FreeBSD.org">DocEng</holder>
     </copyright>
 
     <pubdate role="rcs">$FreeBSD$</pubdate>
 
     <releaseinfo>$FreeBSD$</releaseinfo>
 
     &bookinfo.legalnotice;
  
     <abstract>
       <para>Thank you for becoming a part of the FreeBSD Documentation
         Project. Your contribution is extremely valuable.</para>
 
       <para>This primer covers everything you will need to know in order
         to start contributing to the FreeBSD Documentation Project, from
         the tools and software you will be using (both mandatory and
         recommended) to the philosophy behind the Documentation 
         Project.</para>
 
       <para>This document is a work in progress, and is not complete. Sections
 	that are known to be incomplete are indicated with a
 	<literal>*</literal> in their name.</para>
     </abstract>
   </bookinfo>
 
   <preface id="preface">
     <title>Preface</title>
 
     <sect1 id="preface-prompts">
       <title>Shell Prompts</title>
       
       <para>The following table shows the default system prompt and superuser
 	prompt. The examples will use this prompt to indicate which user you
 	should be running the example as.</para>
 
       <informaltable frame="none">
 	<tgroup cols="2">
 	  <thead>
 	    <row>
 	      <entry>User</entry>
 	      <entry>Prompt</entry>
 	    </row>
 	  </thead>
 	  
 	  <tbody>
 	    <row>
 	      <entry>Normal user</entry>
 	      <entry>&prompt.user;</entry>
 	    </row>
 
 	    <row>
 	      <entry><username>root</username></entry>
 	      <entry>&prompt.root;</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </informaltable>
     </sect1>
     
     <sect1 id="preface-conventions">
       <title>Typographic Conventions</title>
 
       <para>The following table describes the typographic conventions used in
 	this book.</para>
 
       <informaltable frame="none">
 	<tgroup cols="2">
 	  <thead>
 	    <row>
 	      <entry>Meaning</entry>
 	      <entry>Examples</entry>
 	    </row>
 	  </thead>
 	  
 	  <tbody>
 	    <row>
 	      <entry>The name of commands, files, and directories. On screen
 		computer output.</entry>
 	      <entry><para>Edit your <filename>.login</filename>
 		  file.</para><para>Use <command>ls -a</command> to list all
 		  files.</para><para><screen>You have mail.</screen>
 		</para></entry>
 	    </row>
 
 	    <row>
 	      <entry>What you type, when contrasted with on-screen computer
 		output.</entry>
 
 	      <entry><screen>&prompt.user; <userinput>su</userinput>
 Password:</screen></entry>
 	    </row>
 
 	    <row>
 	      <entry>Manual page references.</entry>
 
 	      <entry>Use <citerefentry>
 		  <refentrytitle>su</refentrytitle>
 		  <manvolnum>1</manvolnum>
 		</citerefentry> to change user names.</entry>
 	    </row>
 
 	    <row>
 	      <entry>User and group names</entry>
 
 	      <entry>Only <username>root</username> can do this.</entry>
 	    </row>
 
 	    <row>
 	      <entry>Emphasis</entry>
 
 	      <entry>You <emphasis>must</emphasis> do this.</entry>
 	    </row>
 
 	    <row>
 	      <entry>Command line variables; replace with the real name or
 		variable.</entry>
 
 	      <entry>To delete a file, type <command>rm <filename><replaceable>filename</replaceable></filename></command></entry>
 	    </row>
 
 	    <row>
 	      <entry>Environment variables</entry>
 
 	      <entry><envar>$HOME</envar> is your home directory.</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </informaltable>
     </sect1>
 
     <sect1 id="preface-notes">
       <title>Notes, tips, important information, warnings, and examples</title>
 
       <para>Within the text appear notes, warnings, and examples.</para>
 
       <note>
 	<para>Notes are represented like this, and contain information that
 	  you should take note of, as it may affect what you do.</para>
       </note>
 
       <tip>
 	<para>Tips are represented like this, and contain information that you 
 	  might find useful, or lead to an easier way to do something.</para>
       </tip>
 
       <important>
 	<para>Important information is represented like this.  Typically they
 	  flag extra steps you may need to carry out.</para>
       </important>
 
       <warning>
 	<para>Warnings are represented like this, and contain information
 	  warning you about possible damage if you do not follow the
 	  instructions. This damage may be physical, to your hardware or to
 	  you, or it may be non-physical, such as the inadvertent deletion of
 	  important files.</para>
       </warning>
 
       <example>
 	<title>A sample example</title>
 
 	<para>Examples are represented like this, and typically contain
 	  examples you should walk through, or show you what the results of a
 	  particular action should be.</para>
       </example>
     </sect1>
 
     <sect1 id="preface-acknowledgements">
       <title>Acknowledgments</title>
 
       <para>My thanks to Sue Blake, Patrick Durusau, Jon Hamilton, Peter
 	Flynn, and Christopher Maden, who took the time to read early drafts
 	of this document and offer many valuable comments and
 	criticisms.</para>
     </sect1>
   </preface>
   
   &chap.overview;
   &chap.tools;
   &chap.sgml-primer;
   &chap.sgml-markup;
   &chap.stylesheets;
   &chap.structure;
   &chap.doc-build;
   &chap.the-website;
   &chap.translations;
   &chap.writing-style;
   &chap.psgml-mode;
   &chap.see-also;
 
   &app.examples;
 
 <!--
   &index;  
 -->
 </book>
 
 <!--
      Local Variables:
      mode: sgml
      sgml-indent-data: t
      sgml-omittag: nil
      sgml-always-quote-attributes: t
      End:
 -->
diff --git a/en_US.ISO8859-1/books/fdp-primer/examples/appendix.sgml b/en_US.ISO8859-1/books/fdp-primer/examples/appendix.sgml
index 67c051e207..7833d5d0bc 100644
--- a/en_US.ISO8859-1/books/fdp-primer/examples/appendix.sgml
+++ b/en_US.ISO8859-1/books/fdp-primer/examples/appendix.sgml
@@ -1,355 +1,355 @@
 <!-- Copyright (c) 2000 Nik Clayton, All rights reserved.
 
      Redistribution and use in source (SGML DocBook) and 'compiled' forms
      (SGML HTML, PDF, PostScript, RTF and so forth) with or without
      modification, are permitted provided that the following conditions
      are met:
 
       1. Redistributions of source code (SGML DocBook) must retain the above
          copyright notice, this list of conditions and the following
          disclaimer as the first lines of this file unmodified.
 
       2. Redistributions in compiled form (transformed to other DTDs,
          converted to PDF, PostScript, RTF and other formats) must reproduce
          the above copyright notice, this list of conditions and the
          following disclaimer in the documentation and/or other materials
          provided with the distribution.
 
      THIS DOCUMENTATION IS PROVIDED BY NIK CLAYTON "AS IS" AND ANY EXPRESS OR
      IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
      OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
      DISCLAIMED. IN NO EVENT SHALL NIK CLAYTON BE LIABLE FOR ANY DIRECT,
      INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
      (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
      SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
      HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
      STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
      ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE
      POSSIBILITY OF SUCH DAMAGE.
 
      $FreeBSD$
 -->
 
 <appendix id="examples">
   <title>Examples</title>
 
   <para>This appendix contains example SGML files and command lines you can
     use to convert them from one output format to another.  If you have
     successfully installed the Documentation Project tools then you should
     be able to use these examples directly.</para>
 
   <para>These examples are not exhaustive&mdash;they do not contain all the
     elements you might want to use, particularly in your document's front
     matter.  For more examples of DocBook markup you should examine the SGML
     source for this and other documents, available in the
     <application>CVSup</application> <literal>doc</literal> collection, or
     available online starting at
     <ulink url="http://www.FreeBSD.org/cgi/cvsweb.cgi/doc/"></ulink>.</para>
 
   <para>To avoid confusion, these examples use the standard DocBook 4.1 DTD
     rather than the FreeBSD extension.  They also use the stock stylesheets
     distributed by Norm Walsh, rather than any customisations made to those
     stylesheets by the FreeBSD Documentation Project.  This makes them more
     useful as generic DocBook examples.</para>
 
   <sect1 id="examples-docbook-book">
     <title>DocBook <sgmltag>book</sgmltag></title>
 
     <example>
       <title>DocBook <sgmltag>book</sgmltag></title>
 
       <programlisting><![ CDATA [<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
 
 <book>
   <bookinfo>
     <title>An Example Book</title>
     
     <author>
       <firstname>Your first name</firstname>
       <surname>Your surname</surname>
       <affiliation>
         <address><email>foo@example.com</email></address>
       </affiliation>
     </author>
 
     <copyright>
       <year>2000</year>
       <holder>Copyright string here</holder>
     </copyright>
 
     <abstract>
       <para>If your book has an abstract then it should go here.</para>
     </abstract>
   </bookinfo>
 
   <preface>
     <title>Preface</title>
 
     <para>Your book may have a preface, in which case it should be placed
       here.</para>
   </preface>
       
   <chapter>
     <title>My first chapter</title>
 
     <para>This is the first chapter in my book.</para>
 
     <sect1>
       <title>My first section</title>
 
       <para>This is the first section in my book.</para>
     </sect1>
   </chapter>
 </book>]]></programlisting>
     </example>
   </sect1>
 
   <sect1 id="examples-docbook-article">
     <title>DocBook <sgmltag>article</sgmltag></title>
 
     <example>
       <title>DocBook <sgmltag>article</sgmltag></title>
 
       <programlisting><![ CDATA [<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
 
 <article>
   <articleinfo>
     <title>An example article</title>
 
     <author>
       <firstname>Your first name</firstname>
       <surname>Your surname</surname>
       <affiliation>
         <address><email>foo@example.com</email></address>
       </affiliation>
     </author>
 
     <copyright>
       <year>2000</year>
       <holder>Copyright string here</holder>
     </copyright>
 
     <abstract>
       <para>If your article has an abstract then it should go here.</para>
     </abstract>
   </articleinfo>
 
   <sect1>
     <title>My first section</title>
 
     <para>This is the first section in my article.</para>
 
     <sect2>
       <title>My first sub-section</title>
 
       <para>This is the first sub-section in my article.</para>
     </sect2>	
   </sect1>
 </article>]]></programlisting>
     </example>
   </sect1>
 
   <sect1 id="examples-formatted">
     <title>Producing formatted output</title>
 
     <para>This section assumes that you have installed the software listed in
       the <filename role="package">textproc/docproj</filename> port, either by hand, or by
       using the port.  Further, it is assumed that your software is installed
       in subdirectories under <filename>/usr/local/</filename>, and the
       directory where binaries have been installed is in your
       <envar>PATH</envar>.  Adjust the paths as necessary for your
       system.</para>
 
     <sect2>
       <title>Using Jade</title>
 
       <example>
 	<title>Converting DocBook to HTML (one large file)</title>
 	
 	<screen>&prompt.user; <userinput>jade -V nochunks \  <co id="examples-co-jade-1-nochunks">
     -c /usr/local/share/sgml/docbook/dsssl/modular/catalog \ <co id="examples-co-jade-1-catalog">
     -c /usr/local/share/sgml/docbook/catalog \
     -c /usr/local/share/sgml/jade/catalog \
     -d /usr/local/share/sgml/docbook/dsssl/modular/html/docbook.dsl \<co id="examples-co-jade-1-dsssl">
     -t sgml <co id="examples-co-jade-1-transform"> file.sgml > file.html <co id="examples-co-jade-1-filename"></userinput></screen>
 
 	<calloutlist>
 	  <callout arearefs="examples-co-jade-1-nochunks">
 	    <para>Specifies the <literal>nochunks</literal> parameter to the
 	      stylesheets, forcing all output to be written to
 	      <abbrev>STDOUT</abbrev> (using Norm Walsh's stylesheets).</para>
 	  </callout>
 
 	  <callout arearefs="examples-co-jade-1-catalog">
 	    <para>Specifies the catalogs that Jade will need to process.
 	      Three catalogs are required.  The first is a catalog that
 	      contains information about the DSSSL stylesheets.  The second
 	      contains information about the DocBook DTD.  The third contains
 	      information specific to Jade.</para>
 	  </callout>
 
 	  <callout arearefs="examples-co-jade-1-dsssl">
 	    <para>Specifies the full path to the DSSSL stylesheet that Jade
 	      will use when processing the document.</para>
 	  </callout>
 
 	  <callout arearefs="examples-co-jade-1-transform">
 	    <para>Instructs Jade to perform a
 	      <emphasis>transformation</emphasis> from one DTD to another.  In 
 	      this case, the input is being transformed from the DocBook DTD
 	      to the HTML DTD.</para>
 	  </callout>
 
 	  <callout arearefs="examples-co-jade-1-filename">
 	    <para>Specifies the file that Jade should process, and redirects
 	      output to the specified <filename>.html</filename> file.</para>
 	  </callout>
 	</calloutlist>
       </example>
 
       <example>
 	<title>Converting DocBook to HTML (several small files)</title>
 	
 	<screen>&prompt.user; <userinput>jade \
     -c /usr/local/share/sgml/docbook/dsssl/modular/catalog \ <co id="examples-co-jade-2-catalog">
     -c /usr/local/share/sgml/docbook/catalog \
     -c /usr/local/share/sgml/jade/catalog \
     -d /usr/local/share/sgml/docbook/dsssl/modular/html/docbook.dsl \<co id="examples-co-jade-2-dsssl">
     -t sgml <co id="examples-co-jade-2-transform"> <replaceable>file</replaceable>.sgml <co id="examples-co-jade-2-filename"></userinput></screen>
 
 	<calloutlist>
 	  <callout arearefs="examples-co-jade-2-catalog">
 	    <para>Specifies the catalogs that Jade will need to process.
 	      Three catalogs are required.  The first is a catalog that
 	      contains information about the DSSSL stylesheets.  The second
 	      contains information about the DocBook DTD.  The third contains
 	      information specific to Jade.</para>
 	  </callout>
 
 	  <callout arearefs="examples-co-jade-2-dsssl">
 	    <para>Specifies the full path to the DSSSL stylesheet that Jade
 	      will use when processing the document.</para>
 	  </callout>
 
 	  <callout arearefs="examples-co-jade-2-transform">
 	    <para>Instructs Jade to perform a
 	      <emphasis>transformation</emphasis> from one DTD to another.  In 
 	      this case, the input is being transformed from the DocBook DTD
 	      to the HTML DTD.</para>
 	  </callout>
 
 	  <callout arearefs="examples-co-jade-2-filename">
 	    <para>Specifies the file that Jade should process.  The
 	      stylesheets determine how the individual HTML files will be
 	      named, and the name of the <quote>root</quote> file (i.e., the 
 	      one that contains the start of the document.</para>
 	  </callout>
 	</calloutlist>
 
 	<para>This example may still only generate one HTML file, depending on 
 	  the structure of the document you are processing, and the
 	  stylesheet's rules for splitting output.</para>
       </example>
 
       <example id="examples-docbook-postscript">
 	<title>Converting DocBook to Postscript</title>
 
-	<para>The source SGML file must be converted to a TeX file.</para>
+	<para>The source SGML file must be converted to a &tex; file.</para>
 
 	<screen>&prompt.user; <userinput>jade -Vtex-backend \ <co id="examples-co-jade-3-tex-backend">
     -c /usr/local/share/sgml/docbook/dsssl/modular/catalog \ <co id="examples-co-jade-3-catalog">
     -c /usr/local/share/sgml/docbook/catalog \
     -c /usr/local/share/sgml/jade/catalog \
     -d /usr/local/share/sgml/docbook/dsssl/modular/print/docbook.dsl \<co id="examples-co-jade-3-dsssl">
     -t tex <co id="examples-co-jade-3-tex"> <replaceable>file</replaceable>.sgml</userinput></screen>
 
 	<calloutlist>
 	  <callout arearefs="examples-co-jade-3-tex-backend">
 	    <para>Customises the stylesheets to use various options
-	      specific to producing output for TeX.</para>
+	      specific to producing output for &tex;.</para>
 	  </callout>
 	  
 	  <callout arearefs="examples-co-jade-3-catalog">
 	    <para>Specifies the catalogs that Jade will need to process. Three
 	      catalogs are required.  The first is a catalog that contains
 	      information about the DSSSL stylesheets.  The second contains
 	      information about the DocBook DTD.  The third contains
 	      information specific to Jade.</para>
 	  </callout>
 
 	  <callout arearefs="examples-co-jade-3-dsssl">
 	    <para>Specifies the full path to the DSSSL stylesheet that
 	      Jade will use when processing the document.</para>
 	  </callout>
 
 	  <callout arearefs="examples-co-jade-3-tex">
-	    <para>Instructs Jade to convert the output to TeX.</para>
+	    <para>Instructs Jade to convert the output to &tex;.</para>
 	  </callout>
 	</calloutlist>
 
 	<para>The generated <filename>.tex</filename> file must now be run 
 	  through <command>tex</command>, specifying the
 	  <literal>&amp;jadetex</literal> macro package.</para>
 	    
 	<screen>&prompt.user; <userinput>tex "&amp;jadetex" <replaceable>file</replaceable>.tex</userinput></screen>
 
 	<para>You have to run <command>tex</command> <emphasis>at
 	  least</emphasis> three times.  The first run processes the
 	  document, and determines areas of the document which are referenced
 	  from other parts of the document, for use in indexing, and so
 	  on.</para>
 
 	<para>Do not be alarmed if you see warning messages such as
 	  <literal>LaTeX Warning: Reference `136' on page 5 undefined on input
 	  line 728.</literal> at this point.</para>
 	
 	<para>The second run reprocesses the document now that certain pieces
 	  of information are known (such as the document's page length).  This
 	  allows index entries and other cross-references to be fixed
 	  up.</para>
 
 	<para>The third pass performs any final cleanup necessary.</para>
 	
 	<para>The output from this stage will be
 	  <filename><replaceable>file</replaceable>.dvi</filename>.</para>
 	
 	<para>Finally, run <command>dvips</command> to convert the
 	  <filename>.dvi</filename> file to Postscript.</para>
 
 	<screen>&prompt.user; <userinput>dvips -o <replaceable>file</replaceable>.ps <replaceable>file.dvi</replaceable></userinput></screen>
       </example>
 
       <example>
 	<title>Converting DocBook to PDF</title>
 
 	<para>The first part of this process is identical to that when
 	  converting DocBook to Postscript, using the same
 	  <command>jade</command> command line (<xref
 	    linkend="examples-docbook-postscript">).</para>
 
 	<para>When the <filename>.tex</filename> file has been generated you
 	  run pdfTeX.  However, use the &amp;pdfjadetex macro package
 	  instead.</para>
 
 	<screen>&prompt.user; <userinput>pdftex "&amp;pdfjadetex" <replaceable>file</replaceable>.tex</userinput></screen>
 
 	<para>Again, run this command three times.</para>
 
 	<para>This will generate
 	  <filename><replaceable>file</replaceable>.pdf</filename>, which does 
 	  not need to be processed any further.</para>
       </example>
     </sect2>
   </sect1>
 </appendix>
 
 <!--
      Local Variables:
      mode: sgml
      sgml-declaration: "../appendix.decl"
      sgml-indent-data: t
      sgml-omittag: nil
      sgml-always-quote-attributes: t
      sgml-parent-document: ("../book.sgml" "part" "appendix")
      End:
 -->
diff --git a/en_US.ISO8859-1/books/fdp-primer/tools/chapter.sgml b/en_US.ISO8859-1/books/fdp-primer/tools/chapter.sgml
index a9490faf3d..3f5afc990f 100644
--- a/en_US.ISO8859-1/books/fdp-primer/tools/chapter.sgml
+++ b/en_US.ISO8859-1/books/fdp-primer/tools/chapter.sgml
@@ -1,291 +1,291 @@
 <!-- Copyright (c) 1998, 1999 Nik Clayton, All rights reserved.
 
      Redistribution and use in source (SGML DocBook) and 'compiled' forms
      (SGML, HTML, PDF, PostScript, RTF and so forth) with or without
      modification, are permitted provided that the following conditions
      are met:
 
       1. Redistributions of source code (SGML DocBook) must retain the above
          copyright notice, this list of conditions and the following
          disclaimer as the first lines of this file unmodified.
 
       2. Redistributions in compiled form (transformed to other DTDs,
          converted to PDF, PostScript, RTF and other formats) must reproduce
          the above copyright notice, this list of conditions and the
          following disclaimer in the documentation and/or other materials
          provided with the distribution.
 
      THIS DOCUMENTATION IS PROVIDED BY NIK CLAYTON "AS IS" AND ANY EXPRESS OR
      IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
      OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
      DISCLAIMED. IN NO EVENT SHALL NIK CLAYTON BE LIABLE FOR ANY DIRECT,
      INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
      (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
      SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
      HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
      STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
      ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE
      POSSIBILITY OF SUCH DAMAGE.
 
      $FreeBSD$
 -->
 
 <chapter id="tools">
   <title>Tools</title>
   
   <para>The FDP uses a number of different software tools to help
     manage the FreeBSD documentation, convert it to different output
     formats, and so on.  You will need to use these tools yourself if
     you are to work with the FreeBSD documentation.</para>                    
 
   <para>All these tools are available as FreeBSD Ports and Packages,
     greatly simplifying the work you have to do to install
     them.</para>                                                              
   
   <para>You will need to install these tools before you work through
     any of the examples in later chapters.  The actual usage of these
     tools is covered in later chapters.</para>     
 
   <tip>
     <title>Use <filename role="package">textproc/docproj</filename> if possible</title>
 
     <para>You can save yourself a lot of time if you install the
       <filename role="package">textproc/docproj</filename> port.  This is a
       <emphasis>meta-port</emphasis> which does not contain any software
       itself.  Instead, it depends on various other ports being installed
       correctly.  Installing this port <emphasis>should</emphasis>
       automatically download and install all of the packages listed in this
       chapter that you need.</para>
 
     <para>One of the packages that you might need is the JadeTeX macro set.
-      In turn, this macro set requires TeX to be installed.  TeX is a large
+      In turn, this macro set requires &tex; to be installed.  &tex; is a large
       package, and you only need it if you want to produce Postscript or PDF
       output.</para>
 
     <para>To save yourself time and space you must specify whether or not you
       want JadeTeX (and therefore TeX) installed when you install this port.
       Either do:</para>
 
       <screen>&prompt.root; <userinput>make JADETEX=yes install</userinput></screen>
 
     <para>or</para>
 
       <screen>&prompt.root; <userinput>make JADETEX=no install</userinput></screen>
 
     <para>as necessary.  Alternatively you may install <filename
       role="package">textproc/docproj-jadetex</filename> or <filename
       role="package">textproc/docproj-nojadetex</filename>.  These slave ports
       define the <makevar>JADETEX</makevar> variable for you, therefore they
       will install the same suite of applications on your machine.
       Note that you can produce only HTML or ASCII
       text output if you do not install <application>JadeTeX</application>.
       PostScript or PDF output require <application>TeX</application>.</para>
   </tip>
 
   <sect1 id="tools-mandatory">
     <title>Mandatory tools</title>
 
     <sect2>
       <title>Software</title>
       
       <para>These programs are required before you can usefully work with the
 	FreeBSD documentation, and they will allow you to convert the
 	documentation to HTML, plain text, and RTF formats.  They are all
 	included in <filename role="package">textproc/docproj</filename>.</para>
       
       <variablelist>
 	<varlistentry>
 	  <term><application>SP</application>
 	    (<filename role="package">textproc/sp</filename>)</term>
 	  
 	  <listitem>
 	    <para>A suite of applications, including a validating SGML parser,
 	      and an SGML normaliser.</para>
 	  </listitem>
 	</varlistentry>
 	
 	<varlistentry>
 	  <term><application>Jade</application>
 	    (<filename role="package">textproc/jade</filename>)</term>
 	  
 	  <listitem>
 	    <para>A DSSSL implementation.  Used for converting marked up
 	      documents to other formats, including HTML and TeX.</para>
 	  </listitem>
 	</varlistentry>
 	
 	<varlistentry>
 	  <term><application>Tidy</application>
 	    (<filename role="package">www/tidy</filename>)</term>
 	  
 	  <listitem>
 	    <para>An HTML 'pretty printer', used to reformat some of the
 	      automatically generated HTML so that it is easier to
 	      follow.</para>
 	  </listitem>
 	</varlistentry>
 	
 	<varlistentry>
 	  <term><application>Links</application>
 	    (<filename role="package">www/links</filename>)</term>
 	  
 	  <listitem>
 	    <para>A text-mode WWW browser that can also convert
 	      HTML files to plain text.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><application>peps</application>
 	    (<filename role="package">graphics/peps</filename>)</term>
 	  
 	  <listitem>
 	    <para>Some of the documentation includes images, some of which are
 	      stored as EPS files.  These must be converted to PNG before most
 	      web browsers will display them.</para>
 	  </listitem>
 	</varlistentry>
       </variablelist>
     </sect2>
 
     <sect2>
       <title>DTDs and Entities</title>
 
       <para>These are the DTDs and entity sets used by the FDP.  They need to
 	be installed before you can work with any of the documentation.</para>
       
       <variablelist>
 	<varlistentry>
 	  <term>HTML DTD (<filename role="package">textproc/html</filename>)</term>
 	  
 	  <listitem>
 	    <para>HTML is the markup language of choice for the World Wide
 	      Web, and is used throughout the FreeBSD web site.</para>
 	  </listitem>
 	</varlistentry>
 	
 	<varlistentry>
 	  <term>DocBook DTD (<filename role="package">textproc/docbook</filename>)</term>
 	  
 	  <listitem>
 	    <para>DocBook is designed for marking up technical documentation.
 	      All the FreeBSD documentation is written in DocBook.</para>
 	  </listitem>
 	</varlistentry>
 	
 	<varlistentry>
 	  <term>ISO 8879 entities
 	    (<filename role="package">textproc/iso8879</filename>)</term>
 	  
 	  <listitem>
 	    <para>19 of the ISO 8879:1986 character entity sets used by many
 	      DTDs.  Includes named mathematical symbols, additional
 	      characters in the 'Latin' character set (accents, diacriticals,
 	      and so on), and Greek symbols.</para>
 	  </listitem>
 	</varlistentry>
       </variablelist>
     </sect2>
 
     <sect2>
       <title>Stylesheets</title>
 
       <para>The stylesheets are used when converting and formatting the
 	documentation for display on screen, printing, and so on.</para>
       
       <variablelist>
 	<varlistentry>
 	  <term>Modular DocBook Stylesheets
 	    (<filename role="package">textproc/dsssl-docbook-modular</filename>)</term>
 	  
 	  <listitem>
 	    <para>The Modular DocBook Stylesheets are used when converting
 	      documentation marked up in DocBook to other formats, such as
 	      HTML or RTF.</para>
 	  </listitem>
 	</varlistentry>
       </variablelist>
     </sect2>
   </sect1>
 
   <sect1 id="tools-optional">
     <title>Optional tools</title>
 
     <para>You do not need to have any of the following installed.  However,
       you may find it easier to work with the documentation if you do, and
       they may give you more flexibility in the output formats that can be
       generated.</para>
 
     <sect2>
       <title>Software</title>
       
       <variablelist>
 	<varlistentry>
 	  <term><application>JadeTeX</application> and
 	    <application>teTeX</application>
 	    (<filename role="package">print/jadetex</filename> and
 	    <filename role="package">print/teTeX</filename>)</term>
 	  
 	  <listitem>
 	    <para><application>Jade</application> and
 	      <application>teTeX</application> are used to convert DocBook
 	      documents to DVI, Postscript, and PDF formats.  The
 	      <application>JadeTeX</application> macros are needed in order to
 	      do this.</para>
 
 	    <para>If you do not intend to convert your documentation to one of
 	      these formats (i.e., HTML, plain text, and RTF are sufficient)
 	      then you do not need to install
 	      <application>JadeTeX</application> and
 	      <application>teTeX</application>.  This can be a significant
 	      space and time saver, as <application>teTeX</application> is
 	      over 30MB in size.</para>
 
 	    <important>
 	      <para>If you decide to install
 		<application>JadeTeX</application> and
 		<application>teTeX</application> then you will need to
 		configure <application>teTeX</application> after
 		<application>JadeTeX</application> has been installed.
 		<filename>print/jadetex/pkg-message</filename> contains
 		detailed instructions explaining what you need to do.</para>
 	    </important>
 	  </listitem>
 	</varlistentry>
 	
 	<varlistentry>
 	  <term><application>Emacs</application> or
 	    <application>XEmacs</application> 
 	    (<filename role="package">editors/emacs</filename> or
 	    <filename role="package">editors/xemacs</filename>)</term>
 	  
 	  <listitem>
 	    <para>Both these editors include a special mode for editing
 	      documents marked up according to an SGML DTD.  This mode
 	      includes commands to reduce the amount of typing you need, and
 	      help reduce the possibility of errors.</para>
 
 	    <para>You do not need to use them; any text editor can be used to
 	      edit marked up documents.  You may find they make you more
 	      efficient.</para>
 	  </listitem>
 	</varlistentry>
       </variablelist>
       
       <para>If anyone has recommendations for other software that is useful
 	when manipulating SGML documents, please let &a.doceng; know, so they
 	can be added to this list.</para>
     </sect2>
   </sect1>
 </chapter>
 
 <!--
      Local Variables:
      mode: sgml
      sgml-declaration: "../chapter.decl"
      sgml-indent-data: t
      sgml-omittag: nil
      sgml-always-quote-attributes: t
      sgml-parent-document: ("../book.sgml" "part" "chapter")
      End:
 -->