os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

* Prepend "sgml-primer-" to id attributes which did not already have it.

Browse source 
*  Add 'id="sgml-primer-marked-sections"' to the "Marked Sections"
    section.
This commit is contained in:
Nik Clayton 1999-07-28 20:04:30 +00:00
parent 11a90fc718
commit 91e1bb6c80
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=5264
3 changed files with 60 additions and 60 deletions
en/tutorials/docproj-primer/sgml-primer
chapter.sgml
en_US.ISO8859-1/books/fdp-primer/sgml-primer
chapter.sgml
en_US.ISO_8859-1/books/fdp-primer/sgml-primer
chapter.sgml

40
en/tutorials/docproj-primer/sgml-primer/chapter.sgml
View file

@ -27,7 +27,7 @@
ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
$Id: chapter.sgml,v 1.4 1999-07-14 19:22:44 nik Exp $
$Id: chapter.sgml,v 1.5 1999-07-28 20:04:30 nik Exp $
-->
<chapter id="sgml-primer">
@ -155,7 +155,7 @@
not touch on how to write a DTD.</para>
</sect1>
<sect1 id="elements">
<sect1 id="sgml-primer-elements">
<title>Elements, tags, and attributes</title>
<para>All the DTDs written in SGML share certain characteristics. This is
@ -515,7 +515,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
</sect2>
</sect1>
<sect1 id="doctype-declaration">
<sect1 id="sgml-primer-doctype-declaration">
<title>The DOCTYPE declaration</title>
<para>The beginning of each document that you write must specify the name
@ -558,7 +558,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
<term><literal>html</literal></term>
<listitem>
<para>Names the first <link linkend="elements">element</link> that
<para>Names the first <link linkend="sgml-primer-elements">element</link> that
will appear in the document.</para>
</listitem>
</varlistentry>
@ -574,7 +574,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
<para><literal>PUBLIC</literal> is not a part of the FPI, but
indicates to the SGML processor how to find the DTD referenced in
the FPI. Other ways of telling the SGML parser how to find the DTD
are shown <link linkend="fpi-alternatives">later</link>.</para>
are shown <link linkend="sgml-primer-fpi-alternatives">later</link>.</para>
</listitem>
</varlistentry>
@ -741,7 +741,7 @@ PUBLIC "-//W3C//DTD HTML 4.0//EN" "4.0/strict.dtd"</programlisting>
</sect3>
</sect2>
<sect2 id="fpi-alternatives">
<sect2 id="sgml-primer-fpi-alternatives">
<title>Alternatives to FPIs</title>
<para>Instead of using an FPI to indicate the DTD that the document
@ -765,7 +765,7 @@ PUBLIC "-//W3C//DTD HTML 4.0//EN" "4.0/strict.dtd"</programlisting>
</sect2>
</sect1>
<sect1 id="sgml-escape">
<sect1 id="sgml-primer-sgml-escape">
<title>Escaping back to SGML</title>
<para>Earlier in this primer I said that SGML is only used when writing a
@ -784,7 +784,7 @@ PUBLIC "-//W3C//DTD HTML 4.0//EN" "4.0/strict.dtd"</programlisting>
might find within a DTD.</para>
<para>As you may just have realised, the <link
linkend="doctype-declaration">DOCTYPE declaration</link> is an example
linkend="sgml-primer-doctype-declaration">DOCTYPE declaration</link> is an example
of SGML syntax that you need to include in your document&hellip;</para>
</sect1>
@ -792,7 +792,7 @@ PUBLIC "-//W3C//DTD HTML 4.0//EN" "4.0/strict.dtd"</programlisting>
<title>Comments</title>
<para>Comments are an SGML construction, and are normally only valid
inside a DTD. However, as <xref linkend="sgml-escape"> shows, it is
inside a DTD. However, as <xref linkend="sgml-primer-sgml-escape"> shows, it is
possible to use SGML syntax within your document.</para>
<para>The delimiters for SGML comments is the string
@ -911,12 +911,12 @@ PUBLIC "-//W3C//DTD HTML 4.0//EN" "4.0/strict.dtd"</programlisting>
different situations; <emphasis>general entities</emphasis> and
<emphasis>parameter entities</emphasis>.</para>
<sect2 id="general-entities">
<sect2 id="sgml-primer-general-entities">
<title>General Entities</title>
<para>You can not use general entities in an SGML context (although you
define them in one). They can only be used in your document. Contrast
this with <link linkend="parameter-entities">parameter
this with <link linkend="sgml-primer-parameter-entities">parameter
entities</link>.</para>
<para>Each general entity has a name. When you want to reference a
@ -968,14 +968,14 @@ PUBLIC "-//W3C//DTD HTML 4.0//EN" "4.0/strict.dtd"</programlisting>
</example>
</sect2>
<sect2 id="parameter-entities">
<sect2 id="sgml-primer-parameter-entities">
<title>Parameter entities</title>
<para>Like <link linkend="general-entities">general entities</link>,
<para>Like <link linkend="sgml-primer-general-entities">general entities</link>,
parameter entities are used to assign names to reusable chunks of
text. However, where as general entities can only be used within your
document, parameter entities can only be used within an <link
linkend="sgml-escape">SGML context</link>.</para>
linkend="sgml-primer-sgml-escape">SGML context</link>.</para>
<para>Parameter entities are defined in a similar way to general
entities. However, instead of using
@ -1088,11 +1088,11 @@ PUBLIC "-//W3C//DTD HTML 4.0//EN" "4.0/strict.dtd"</programlisting>
<sect1>
<title>Using entities to include files</title>
<para>Entities (both <link linkend="general-entities">general</link> and
<link linkend="parameter-entities">parameter</link>) are particularly
useful when used to include one file inside another.</para>
<para>Entities (both <link linkend="sgml-primer-general-entities">general</link> and
<link linkend="sgml-primer-parameter-entities">parameter</link>) are
particularly useful when used to include one file inside another.</para>
<sect2 id="include-using-gen-entities">
<sect2 id="sgml-primer-include-using-gen-entities">
<title>Using general entities to include files</title>
<para>Suppose you have some content for an SGML book organised into
@ -1313,7 +1313,7 @@ PUBLIC "-//W3C//DTD HTML 4.0//EN" "4.0/strict.dtd"</programlisting>
</sect2>
</sect1>
<sect1>
<sect1 id="sgml-primer-marked-sections">
<title>Marked sections</title>
<para>SGML provides a mechanism to indicate that particular pieces of the
@ -1447,7 +1447,7 @@ PUBLIC "-//W3C//DTD HTML 4.0//EN" "4.0/strict.dtd"</programlisting>
comments.</para>
<para>It becomes more useful when you realise you can use <link
linkend="parameter-entities">parameter entities</link> to control
linkend="sgml-primer-parameter-entities">parameter entities</link> to control
this. Remember that parameter entities can only be used in SGML
contexts, and the keyword of a marked section
<emphasis>is</emphasis> an SGML context.</para>

40
en_US.ISO8859-1/books/fdp-primer/sgml-primer/chapter.sgml
View file

@ -27,7 +27,7 @@
ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
$Id: chapter.sgml,v 1.4 1999-07-14 19:22:44 nik Exp $
$Id: chapter.sgml,v 1.5 1999-07-28 20:04:30 nik Exp $
-->
<chapter id="sgml-primer">
@ -155,7 +155,7 @@
not touch on how to write a DTD.</para>
</sect1>
<sect1 id="elements">
<sect1 id="sgml-primer-elements">
<title>Elements, tags, and attributes</title>
<para>All the DTDs written in SGML share certain characteristics. This is
@ -515,7 +515,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
</sect2>
</sect1>
<sect1 id="doctype-declaration">
<sect1 id="sgml-primer-doctype-declaration">
<title>The DOCTYPE declaration</title>
<para>The beginning of each document that you write must specify the name
@ -558,7 +558,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
<term><literal>html</literal></term>
<listitem>
<para>Names the first <link linkend="elements">element</link> that
<para>Names the first <link linkend="sgml-primer-elements">element</link> that
will appear in the document.</para>
</listitem>
</varlistentry>
@ -574,7 +574,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
<para><literal>PUBLIC</literal> is not a part of the FPI, but
indicates to the SGML processor how to find the DTD referenced in
the FPI. Other ways of telling the SGML parser how to find the DTD
are shown <link linkend="fpi-alternatives">later</link>.</para>
are shown <link linkend="sgml-primer-fpi-alternatives">later</link>.</para>
</listitem>
</varlistentry>
@ -741,7 +741,7 @@ PUBLIC "-//W3C//DTD HTML 4.0//EN" "4.0/strict.dtd"</programlisting>
</sect3>
</sect2>
<sect2 id="fpi-alternatives">
<sect2 id="sgml-primer-fpi-alternatives">
<title>Alternatives to FPIs</title>
<para>Instead of using an FPI to indicate the DTD that the document
@ -765,7 +765,7 @@ PUBLIC "-//W3C//DTD HTML 4.0//EN" "4.0/strict.dtd"</programlisting>
</sect2>
</sect1>
<sect1 id="sgml-escape">
<sect1 id="sgml-primer-sgml-escape">
<title>Escaping back to SGML</title>
<para>Earlier in this primer I said that SGML is only used when writing a
@ -784,7 +784,7 @@ PUBLIC "-//W3C//DTD HTML 4.0//EN" "4.0/strict.dtd"</programlisting>
might find within a DTD.</para>
<para>As you may just have realised, the <link
linkend="doctype-declaration">DOCTYPE declaration</link> is an example
linkend="sgml-primer-doctype-declaration">DOCTYPE declaration</link> is an example
of SGML syntax that you need to include in your document&hellip;</para>
</sect1>
@ -792,7 +792,7 @@ PUBLIC "-//W3C//DTD HTML 4.0//EN" "4.0/strict.dtd"</programlisting>
<title>Comments</title>
<para>Comments are an SGML construction, and are normally only valid
inside a DTD. However, as <xref linkend="sgml-escape"> shows, it is
inside a DTD. However, as <xref linkend="sgml-primer-sgml-escape"> shows, it is
possible to use SGML syntax within your document.</para>
<para>The delimiters for SGML comments is the string
@ -911,12 +911,12 @@ PUBLIC "-//W3C//DTD HTML 4.0//EN" "4.0/strict.dtd"</programlisting>
different situations; <emphasis>general entities</emphasis> and
<emphasis>parameter entities</emphasis>.</para>
<sect2 id="general-entities">
<sect2 id="sgml-primer-general-entities">
<title>General Entities</title>
<para>You can not use general entities in an SGML context (although you
define them in one). They can only be used in your document. Contrast
this with <link linkend="parameter-entities">parameter
this with <link linkend="sgml-primer-parameter-entities">parameter
entities</link>.</para>
<para>Each general entity has a name. When you want to reference a
@ -968,14 +968,14 @@ PUBLIC "-//W3C//DTD HTML 4.0//EN" "4.0/strict.dtd"</programlisting>
</example>
</sect2>
<sect2 id="parameter-entities">
<sect2 id="sgml-primer-parameter-entities">
<title>Parameter entities</title>
<para>Like <link linkend="general-entities">general entities</link>,
<para>Like <link linkend="sgml-primer-general-entities">general entities</link>,
parameter entities are used to assign names to reusable chunks of
text. However, where as general entities can only be used within your
document, parameter entities can only be used within an <link
linkend="sgml-escape">SGML context</link>.</para>
linkend="sgml-primer-sgml-escape">SGML context</link>.</para>
<para>Parameter entities are defined in a similar way to general
entities. However, instead of using
@ -1088,11 +1088,11 @@ PUBLIC "-//W3C//DTD HTML 4.0//EN" "4.0/strict.dtd"</programlisting>
<sect1>
<title>Using entities to include files</title>
<para>Entities (both <link linkend="general-entities">general</link> and
<link linkend="parameter-entities">parameter</link>) are particularly
useful when used to include one file inside another.</para>
<para>Entities (both <link linkend="sgml-primer-general-entities">general</link> and
<link linkend="sgml-primer-parameter-entities">parameter</link>) are
particularly useful when used to include one file inside another.</para>
<sect2 id="include-using-gen-entities">
<sect2 id="sgml-primer-include-using-gen-entities">
<title>Using general entities to include files</title>
<para>Suppose you have some content for an SGML book organised into
@ -1313,7 +1313,7 @@ PUBLIC "-//W3C//DTD HTML 4.0//EN" "4.0/strict.dtd"</programlisting>
</sect2>
</sect1>
<sect1>
<sect1 id="sgml-primer-marked-sections">
<title>Marked sections</title>
<para>SGML provides a mechanism to indicate that particular pieces of the
@ -1447,7 +1447,7 @@ PUBLIC "-//W3C//DTD HTML 4.0//EN" "4.0/strict.dtd"</programlisting>
comments.</para>
<para>It becomes more useful when you realise you can use <link
linkend="parameter-entities">parameter entities</link> to control
linkend="sgml-primer-parameter-entities">parameter entities</link> to control
this. Remember that parameter entities can only be used in SGML
contexts, and the keyword of a marked section
<emphasis>is</emphasis> an SGML context.</para>

40
en_US.ISO_8859-1/books/fdp-primer/sgml-primer/chapter.sgml
View file

@ -27,7 +27,7 @@
ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
$Id: chapter.sgml,v 1.4 1999-07-14 19:22:44 nik Exp $
$Id: chapter.sgml,v 1.5 1999-07-28 20:04:30 nik Exp $
-->
<chapter id="sgml-primer">
@ -155,7 +155,7 @@
not touch on how to write a DTD.</para>
</sect1>
<sect1 id="elements">
<sect1 id="sgml-primer-elements">
<title>Elements, tags, and attributes</title>
<para>All the DTDs written in SGML share certain characteristics. This is
@ -515,7 +515,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
</sect2>
</sect1>
<sect1 id="doctype-declaration">
<sect1 id="sgml-primer-doctype-declaration">
<title>The DOCTYPE declaration</title>
<para>The beginning of each document that you write must specify the name
@ -558,7 +558,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
<term><literal>html</literal></term>
<listitem>
<para>Names the first <link linkend="elements">element</link> that
<para>Names the first <link linkend="sgml-primer-elements">element</link> that
will appear in the document.</para>
</listitem>
</varlistentry>
@ -574,7 +574,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
<para><literal>PUBLIC</literal> is not a part of the FPI, but
indicates to the SGML processor how to find the DTD referenced in
the FPI. Other ways of telling the SGML parser how to find the DTD
are shown <link linkend="fpi-alternatives">later</link>.</para>
are shown <link linkend="sgml-primer-fpi-alternatives">later</link>.</para>
</listitem>
</varlistentry>
@ -741,7 +741,7 @@ PUBLIC "-//W3C//DTD HTML 4.0//EN" "4.0/strict.dtd"</programlisting>
</sect3>
</sect2>
<sect2 id="fpi-alternatives">
<sect2 id="sgml-primer-fpi-alternatives">
<title>Alternatives to FPIs</title>
<para>Instead of using an FPI to indicate the DTD that the document
@ -765,7 +765,7 @@ PUBLIC "-//W3C//DTD HTML 4.0//EN" "4.0/strict.dtd"</programlisting>
</sect2>
</sect1>
<sect1 id="sgml-escape">
<sect1 id="sgml-primer-sgml-escape">
<title>Escaping back to SGML</title>
<para>Earlier in this primer I said that SGML is only used when writing a
@ -784,7 +784,7 @@ PUBLIC "-//W3C//DTD HTML 4.0//EN" "4.0/strict.dtd"</programlisting>
might find within a DTD.</para>
<para>As you may just have realised, the <link
linkend="doctype-declaration">DOCTYPE declaration</link> is an example
linkend="sgml-primer-doctype-declaration">DOCTYPE declaration</link> is an example
of SGML syntax that you need to include in your document&hellip;</para>
</sect1>
@ -792,7 +792,7 @@ PUBLIC "-//W3C//DTD HTML 4.0//EN" "4.0/strict.dtd"</programlisting>
<title>Comments</title>
<para>Comments are an SGML construction, and are normally only valid
inside a DTD. However, as <xref linkend="sgml-escape"> shows, it is
inside a DTD. However, as <xref linkend="sgml-primer-sgml-escape"> shows, it is
possible to use SGML syntax within your document.</para>
<para>The delimiters for SGML comments is the string
@ -911,12 +911,12 @@ PUBLIC "-//W3C//DTD HTML 4.0//EN" "4.0/strict.dtd"</programlisting>
different situations; <emphasis>general entities</emphasis> and
<emphasis>parameter entities</emphasis>.</para>
<sect2 id="general-entities">
<sect2 id="sgml-primer-general-entities">
<title>General Entities</title>
<para>You can not use general entities in an SGML context (although you
define them in one). They can only be used in your document. Contrast
this with <link linkend="parameter-entities">parameter
this with <link linkend="sgml-primer-parameter-entities">parameter
entities</link>.</para>
<para>Each general entity has a name. When you want to reference a
@ -968,14 +968,14 @@ PUBLIC "-//W3C//DTD HTML 4.0//EN" "4.0/strict.dtd"</programlisting>
</example>
</sect2>
<sect2 id="parameter-entities">
<sect2 id="sgml-primer-parameter-entities">
<title>Parameter entities</title>
<para>Like <link linkend="general-entities">general entities</link>,
<para>Like <link linkend="sgml-primer-general-entities">general entities</link>,
parameter entities are used to assign names to reusable chunks of
text. However, where as general entities can only be used within your
document, parameter entities can only be used within an <link
linkend="sgml-escape">SGML context</link>.</para>
linkend="sgml-primer-sgml-escape">SGML context</link>.</para>
<para>Parameter entities are defined in a similar way to general
entities. However, instead of using
@ -1088,11 +1088,11 @@ PUBLIC "-//W3C//DTD HTML 4.0//EN" "4.0/strict.dtd"</programlisting>
<sect1>
<title>Using entities to include files</title>
<para>Entities (both <link linkend="general-entities">general</link> and
<link linkend="parameter-entities">parameter</link>) are particularly
useful when used to include one file inside another.</para>
<para>Entities (both <link linkend="sgml-primer-general-entities">general</link> and
<link linkend="sgml-primer-parameter-entities">parameter</link>) are
particularly useful when used to include one file inside another.</para>
<sect2 id="include-using-gen-entities">
<sect2 id="sgml-primer-include-using-gen-entities">
<title>Using general entities to include files</title>
<para>Suppose you have some content for an SGML book organised into
@ -1313,7 +1313,7 @@ PUBLIC "-//W3C//DTD HTML 4.0//EN" "4.0/strict.dtd"</programlisting>
</sect2>
</sect1>
<sect1>
<sect1 id="sgml-primer-marked-sections">
<title>Marked sections</title>
<para>SGML provides a mechanism to indicate that particular pieces of the
@ -1447,7 +1447,7 @@ PUBLIC "-//W3C//DTD HTML 4.0//EN" "4.0/strict.dtd"</programlisting>
comments.</para>
<para>It becomes more useful when you realise you can use <link
linkend="parameter-entities">parameter entities</link> to control
linkend="sgml-primer-parameter-entities">parameter entities</link> to control
this. Remember that parameter entities can only be used in SGML
contexts, and the keyword of a marked section
<emphasis>is</emphasis> an SGML context.</para>