aboutsummaryrefslogtreecommitdiff
path: root/en_US.ISO8859-1/books/fdp-primer/structure/chapter.sgml
diff options
context:
space:
mode:
Diffstat (limited to 'en_US.ISO8859-1/books/fdp-primer/structure/chapter.sgml')
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/structure/chapter.sgml22
1 files changed, 11 insertions, 11 deletions
diff --git a/en_US.ISO8859-1/books/fdp-primer/structure/chapter.sgml b/en_US.ISO8859-1/books/fdp-primer/structure/chapter.sgml
index 4867d25391..ab25b68972 100644
--- a/en_US.ISO8859-1/books/fdp-primer/structure/chapter.sgml
+++ b/en_US.ISO8859-1/books/fdp-primer/structure/chapter.sgml
@@ -83,7 +83,7 @@
subdirectories to further categorize the information. For
example, the files that comprise the &man.make.1;
infrastructure are in <filename>share/mk</filename>, while
- the additional SGML support files (such as the FreeBSD
+ the additional XML support files (such as the FreeBSD
extended DocBook DTD) are in
<filename>share/sgml</filename>.</seg>
</seglistitem>
@@ -124,7 +124,7 @@
<seg>Documentation marked up as a DocBook
<sgmltag>article</sgmltag> (or equivalent). Reasonably
short, and broken up into sections. Normally only available
- as one HTML file.</seg>
+ as one XHTML file.</seg>
</seglistitem>
<seglistitem>
@@ -133,7 +133,7 @@
<seg>Documentation marked up as a DocBook
<sgmltag>book</sgmltag> (or equivalent). Book length, and
broken up into chapters. Normally available as both one
- large HTML file (for people with fast connections, or who
+ large XHTML file (for people with fast connections, or who
want to print it easily from a browser) and as a collection
of linked, smaller files.</seg>
</seglistitem>
@@ -195,7 +195,7 @@
<title><filename>Makefile</filename></title>
<para>The <filename>Makefile</filename> defines some
- variables that affect how the SGML source is converted to
+ variables that affect how the XML source is converted to
other formats, and lists the various source files that
make up the Handbook. It then includes the standard
<filename>doc.project.mk</filename> file, to bring in the
@@ -208,16 +208,16 @@
<para>This is the top level document in the Handbook. It
contains the Handbook's <link
- linkend="sgml-primer-doctype-declaration">DOCTYPE
+ linkend="xml-primer-doctype-declaration">DOCTYPE
declaration</link>, as well as the elements that
describe the Handbook's structure.</para>
<para><filename>book.sgml</filename> uses <link
- linkend="sgml-primer-parameter-entities">parameter
+ linkend="xml-primer-parameter-entities">parameter
entities</link> to load in the files with the
<filename>.ent</filename> extension. These files
(described later) then define <link
- linkend="sgml-primer-general-entities">general
+ linkend="xml-primer-general-entities">general
entities</link> that are used throughout the rest of the
Handbook.</para>
</sect4>
@@ -246,7 +246,7 @@
the entire contents of the chapter will be held in this
file.</para>
- <para>When the HTML version of the Handbook is produced,
+ <para>When the XHTML version of the Handbook is produced,
this will yield <filename>kernelconfig.html</filename>.
This is because of the <literal>id</literal> value, and is
not related to the name of the directory.</para>
@@ -260,7 +260,7 @@
Handbook chapter are stored within <filename
class="directory">share/images/books/handbook</filename>.
Note that localized version of these images should be
- placed in the same directory as the SGML sources for each
+ placed in the same directory as the XML sources for each
chapter. Namespace collisions would be inevitable, and it
is easier to work with several directories with a few
files in them than it is to work with one directory that
@@ -283,12 +283,12 @@
</important>
<para>Each <filename>chapter.sgml</filename> file will not
- be a complete SGML document. In particular, they will not
+ be a complete XML document. In particular, they will not
have their own DOCTYPE lines at the start of the
files.</para>
<para>This is unfortunate as it makes it impossible to treat
- these as generic SGML files and simply convert them to
+ these as generic XML files and simply convert them to
HTML, RTF, PS, and other formats in the same way the main
Handbook is generated. This <emphasis>would</emphasis>
force you to rebuild the Handbook every time you want to