diff options
Diffstat (limited to 'zh_TW.Big5/books/fdp-primer/structure/chapter.xml')
| -rw-r--r-- | zh_TW.Big5/books/fdp-primer/structure/chapter.xml | 45 |
1 files changed, 21 insertions, 24 deletions
diff --git a/zh_TW.Big5/books/fdp-primer/structure/chapter.xml b/zh_TW.Big5/books/fdp-primer/structure/chapter.xml index 8c22d28519..267443420f 100644 --- a/zh_TW.Big5/books/fdp-primer/structure/chapter.xml +++ b/zh_TW.Big5/books/fdp-primer/structure/chapter.xml @@ -31,8 +31,7 @@ $FreeBSD$ Original revision: 1.17 --> - -<chapter id="structure"> +<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="structure"> <title>Structuring documents under <filename>doc/</filename></title> <para>The <filename>doc/</filename> tree is organized in a particular @@ -62,7 +61,7 @@ encodings. It is important that the structure of the documentation tree does not enforce any particular defaults or cultural preferences.</para> - <sect1 id="structure-top"> + <sect1 xml:id="structure-top"> <title>The top level, <filename>doc/</filename></title> <para>There are two types of directory under <filename>doc/</filename>, @@ -86,7 +85,7 @@ </seglistitem> <seglistitem> - <seg><filename><replaceable>lang</replaceable>.<replaceable>encoding</replaceable>/</filename></seg> + <seg><filename>lang.encoding/</filename></seg> <seg>One directory exists for each available translation and encoding of the documentation, for example @@ -101,9 +100,9 @@ </segmentedlist> </sect1> - <sect1 id="structure-locale"> + <sect1 xml:id="structure-locale"> <title>The - <filename><replaceable>lang</replaceable>.<replaceable>encoding</replaceable>/</filename> directories</title> + <filename>lang.encoding/</filename> directories</title> <para>These directories contain the documents themselves. The documentation is split into up to three more categories at this @@ -117,7 +116,7 @@ <seglistitem> <seg><filename>articles</filename></seg> - <seg>Documentation marked up as a DocBook <sgmltag>article</sgmltag> + <seg>Documentation marked up as a DocBook <tag>article</tag> (or equivalent). Reasonably short, and broken up into sections. Normally only available as one HTML file.</seg> </seglistitem> @@ -125,7 +124,7 @@ <seglistitem> <seg><filename>books</filename></seg> - <seg>Documentation marked up as a DocBook <sgmltag>book</sgmltag> (or + <seg>Documentation marked up as a DocBook <tag>book</tag> (or equivalent). Book length, and broken up into chapters. Normally available as both one large HTML file (for people with fast connections, or who want to print it easily from a browser) and @@ -137,18 +136,18 @@ <seg>For translations of the system manual pages. This directory will contain one or more - <filename>man<replaceable>n</replaceable></filename> directories, + <filename>mann</filename> directories, corresponding to the sections that have been translated.</seg> </seglistitem> </segmentedlist> <para>Not every - <filename><replaceable>lang</replaceable>.<replaceable>encoding</replaceable></filename> directory will contain all of these directories. It depends + <filename>lang.encoding</filename> directory will contain all of these directories. It depends on how much translation has been accomplished by that translation team.</para> </sect1> - <sect1 id="structure-document"> + <sect1 xml:id="structure-document"> <title>Document specific information</title> <para>This section contains specific notes about particular documents @@ -162,12 +161,12 @@ <para>The Handbook is written to comply with the FreeBSD DocBook extended DTD.</para> - <para>The Handbook is organized as a DocBook <sgmltag>book</sgmltag>. - It is then divided into <sgmltag>part</sgmltag>s, each of which may - contain several <sgmltag>chapter</sgmltag>s. - <sgmltag>chapter</sgmltag>s are further subdivided into sections - (<sgmltag>sect1</sgmltag>) and subsections (<sgmltag>sect2</sgmltag>, - <sgmltag>sect3</sgmltag>) and so on.</para> + <para>The Handbook is organized as a DocBook <tag>book</tag>. + It is then divided into <tag>part</tag>s, each of which may + contain several <tag>chapter</tag>s. + <tag>chapter</tag>s are further subdivided into sections + (<tag>sect1</tag>) and subsections (<tag>sect2</tag>, + <tag>sect3</tag>) and so on.</para> <sect3> <title>Physical organization</title> @@ -197,13 +196,11 @@ <title><filename>book.xml</filename></title> <para>This is the top level document in the Handbook. It contains - the Handbook's <link - linkend="sgml-primer-doctype-declaration">DOCTYPE + the Handbook's <link linkend="sgml-primer-doctype-declaration">DOCTYPE declaration</link>, as well as the elements that describe the Handbook's structure.</para> - <para><filename>book.xml</filename> uses <link - linkend="sgml-primer-parameter-entities">parameter + <para><filename>book.xml</filename> uses <link linkend="sgml-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 @@ -212,12 +209,12 @@ </sect4> <sect4> - <title><filename><replaceable>directory</replaceable>/chapter.xml</filename></title> + <title><filename>directory/chapter.xml</filename></title> <para>Each chapter in the Handbook is stored in a file called <filename>chapter.xml</filename> in a separate directory from the other chapters. Each directory is named after the value of the - <literal>id</literal> attribute on the <sgmltag>chapter</sgmltag> + <literal>id</literal> attribute on the <tag>chapter</tag> element.</para> <para>For example, if one of the chapter files contains:</para> @@ -240,7 +237,7 @@ <para>In earlier versions of the Handbook the files were stored in the same directory as <filename>book.xml</filename>, and named after the value of the <literal>id</literal> attribute on the - file's <sgmltag>chapter</sgmltag> element. Moving them into + file's <tag>chapter</tag> element. Moving them into separate directories prepares for future plans for the Handbook. Specifically, it will soon be possible to include images in each chapter. It makes more sense for each image to be stored in a |