Spelling Fixes:
* overridable -> overridden * documention -> documentation * preceeding -> preceding * preceeded -> preceded * harddisk -> hard disk * analagous -> analogous * togther -> together * timelines -> time lines * philisophy-> philosophy * differentation -> differentiation * knowledgable -> knowledgeable * occurence -> occurrence * occured -> occurred * greek -> Greek * aready -> already * commandline -> command line * latin -> Latin * seperate -> separate
This commit is contained in:
parent
720c2bf7f4
commit
efda86a986
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=11094
6 changed files with 27 additions and 26 deletions
|
@ -27,7 +27,7 @@
|
|||
ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE
|
||||
POSSIBILITY OF SUCH DAMAGE.
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/fdp-primer/doc-build/chapter.sgml,v 1.5 2001/07/05 08:47:55 dd Exp $
|
||||
$FreeBSD$
|
||||
-->
|
||||
|
||||
<chapter id="doc-build">
|
||||
|
@ -174,7 +174,7 @@ DOC_PREFIX?= ${.CURDIR}/..
|
|||
|
||||
<para><makevar>DOC_PREFIX</makevar> is the path to the root of the
|
||||
FreeBSD Document Project tree. This is not always that easy to
|
||||
find, and is also easily overridable, to allow for flexibility.
|
||||
find, and is also easily overridden, to allow for flexibility.
|
||||
<makevar>.CURDIR</makevar> is a <application>make</application>
|
||||
builtin variable with the path to the current directory.</para>
|
||||
|
||||
|
|
|
@ -69,7 +69,8 @@
|
|||
url="http://www.w3.org/">http://www.w3.org/</ulink>>.</para>
|
||||
|
||||
<para>HTML is used to markup pages on the FreeBSD web site. It should not
|
||||
(generally) be used to mark up other documention, since DocBook offers a
|
||||
(generally) be used to mark up other documentation,
|
||||
since DocBook offers a
|
||||
far richer set of elements to choose from. Consequently, you will
|
||||
normally only encounter HTML pages if you are writing for the web
|
||||
site.</para>
|
||||
|
@ -169,7 +170,7 @@
|
|||
headings (<sgmltag>h2</sgmltag>), which can in turn contain many
|
||||
third level headings. Each
|
||||
<sgmltag>h<replaceable>n</replaceable></sgmltag> element should have
|
||||
the same element, but one further up the hierarchy, preceeding it.
|
||||
the same element, but one further up the hierarchy, preceding it.
|
||||
Leaving gaps in the numbering is to be avoided.</para>
|
||||
|
||||
<example>
|
||||
|
@ -259,7 +260,7 @@
|
|||
<para>Use:</para>
|
||||
|
||||
<programlisting><![ CDATA [<p>An unordered list. Listitems will probably be
|
||||
preceeded by bullets.</p>
|
||||
preceded by bullets.</p>
|
||||
|
||||
<ul>
|
||||
<li>First item</li>
|
||||
|
@ -639,7 +640,7 @@
|
|||
|
||||
<para>If you are linking to a named anchor within the same document
|
||||
then you can omit the document's URL, and just include the name of
|
||||
the anchor (with the preceeding <literal>#</literal>).</para>
|
||||
the anchor (with the preceding <literal>#</literal>).</para>
|
||||
|
||||
<example>
|
||||
<title>Linking to a named part of the same document</title>
|
||||
|
@ -1106,14 +1107,14 @@
|
|||
|
||||
<programlisting><![ CDATA [<warning>
|
||||
<para>Installing FreeBSD may make you want to delete Windows from your
|
||||
harddisk.</para>
|
||||
hard disk.</para>
|
||||
</warning>]]></programlisting>
|
||||
</example>
|
||||
|
||||
<!-- Need to do this outside of the example -->
|
||||
<warning>
|
||||
<para>Installing FreeBSD may make you want to delete Windows from
|
||||
your harddisk.</para>
|
||||
your hard disk.</para>
|
||||
</warning>
|
||||
</sect3>
|
||||
|
||||
|
@ -1137,7 +1138,7 @@
|
|||
HTML, <sgmltag>ul</sgmltag> and <sgmltag>ol</sgmltag>. Each one
|
||||
consists of one or more <sgmltag>listitem</sgmltag> elements, and
|
||||
each <sgmltag>listitem</sgmltag> contains one or more block
|
||||
elements. The <sgmltag>listitem</sgmltag> elements are analagous to
|
||||
elements. The <sgmltag>listitem</sgmltag> elements are analogous to
|
||||
HTML's <sgmltag>li</sgmltag> tags. However, unlike HTML, they are
|
||||
required.</para>
|
||||
|
||||
|
@ -2186,7 +2187,7 @@ This is the file called 'foo2'</screen>
|
|||
<para>The best example of what follows in practice is the
|
||||
<filename>doc/en_US.ISO8859-1/articles/vm-design/</filename> document.
|
||||
If you're unsure of the description that follows, take a look at the
|
||||
files in that directory to see how everything hangs togther.
|
||||
files in that directory to see how everything hangs together.
|
||||
Experiment with creating different formatted versions of the
|
||||
document to see how the image markup appears in the formatted
|
||||
output.</para>
|
||||
|
@ -2199,7 +2200,7 @@ This is the file called 'foo2'</screen>
|
|||
should use will depend on the nature of your image.</para>
|
||||
|
||||
<para>For images that are primarily vector based, such as network
|
||||
diagrams, timelines, and similar, use Encapsulated Postscript, and
|
||||
diagrams, time lines, and similar, use Encapsulated Postscript, and
|
||||
make sure that your images have the <filename>.eps</filename>
|
||||
extension.</para>
|
||||
|
||||
|
|
|
@ -27,7 +27,7 @@
|
|||
ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE
|
||||
POSSIBILITY OF SUCH DAMAGE.
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/fdp-primer/sgml-primer/chapter.sgml,v 1.20 2001/10/02 05:28:56 murray Exp $
|
||||
$FreeBSD$
|
||||
-->
|
||||
|
||||
<chapter id="sgml-primer">
|
||||
|
@ -161,7 +161,7 @@
|
|||
|
||||
<para>All the DTDs written in SGML share certain characteristics. This is
|
||||
hardly surprising, as the philosophy behind SGML will inevitably show
|
||||
through. One of the most obvious manifestations of this philisophy is
|
||||
through. One of the most obvious manifestations of this philosophy is
|
||||
that of <emphasis>content</emphasis> and
|
||||
<emphasis>elements</emphasis>.</para>
|
||||
|
||||
|
@ -185,7 +185,7 @@
|
|||
chunked further into paragraphs, footnotes, character names, and so
|
||||
on.</para>
|
||||
|
||||
<para>Notice how you can make this differentation between different
|
||||
<para>Notice how you can make this differentiation between different
|
||||
elements of the content without resorting to any SGML terms. It really
|
||||
is surprisingly straightforward. You could do this with a highlighter
|
||||
pen and a printout of the book, using different colours to indicate
|
||||
|
@ -265,7 +265,7 @@
|
|||
a defined start and end. The tags mark where the element starts and
|
||||
end.</para>
|
||||
|
||||
<para>When this document (or anyone else knowledgable about SGML) refers
|
||||
<para>When this document (or anyone else knowledgeable about SGML) refers
|
||||
to <quote>the <p> tag</quote> they mean the literal text
|
||||
consisting of the three characters <literal><</literal>,
|
||||
<literal>p</literal>, and <literal>></literal>. But the phrase
|
||||
|
@ -279,7 +279,7 @@
|
|||
<para>Elements can have attributes. An attribute has a name and a value,
|
||||
and is used for adding extra information to the element. This might be
|
||||
information that indicates how the content should be rendered, or might
|
||||
be something that uniquely identifies that occurence of the element, or
|
||||
be something that uniquely identifies that occurrence of the element, or
|
||||
it might be something else.</para>
|
||||
|
||||
<para>An element's attributes are written <emphasis>inside</emphasis> the
|
||||
|
@ -489,7 +489,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
|
|||
generated 2 different errors.</para>
|
||||
|
||||
<para>The first error indicates that content (in this case,
|
||||
characters, rather than the start tag for an element) has occured
|
||||
characters, rather than the start tag for an element) has occurred
|
||||
where the SGML parser was expecting something else. In this case,
|
||||
the parser was expecting to see one of the start tags for elements
|
||||
that are valid inside <sgmltag>head</sgmltag> (such as
|
||||
|
@ -613,7 +613,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
|
|||
ISO owned FPI. For example, the FPI <literal>"ISO
|
||||
8879:1986//ENTITIES Greek Symbols//EN"</literal> lists
|
||||
<literal>ISO 8879:1986</literal> as being the owner for the set
|
||||
of entities for greek symbols. ISO 8879:1986 is the ISO number
|
||||
of entities for Greek symbols. ISO 8879:1986 is the ISO number
|
||||
for the SGML standard.</para>
|
||||
|
||||
<para>Otherwise, this string will either look like
|
||||
|
@ -795,7 +795,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
|
|||
shows, it is possible to use SGML syntax within your document.</para>
|
||||
|
||||
<para>The delimiter for SGML comments is the string
|
||||
<quote><literal>--</literal></quote>. The first occurence of this string
|
||||
<quote><literal>--</literal></quote>. The first occurrence of this string
|
||||
opens a comment, and the second closes it.</para>
|
||||
|
||||
<example>
|
||||
|
|
|
@ -38,7 +38,7 @@
|
|||
|
||||
<para>Get 200MB free disk space. You will need the disk space for the
|
||||
SGML tools, a subset of the CVS tree, temporary build space and the
|
||||
installed web pages. If you aready have installed the SGML tools and
|
||||
installed web pages. If you already have installed the SGML tools and
|
||||
the CVS tree, you need only ~100MB free disk space.</para>
|
||||
|
||||
<note>
|
||||
|
@ -196,13 +196,13 @@
|
|||
</variablelist>
|
||||
|
||||
<para><envar>CVSROOT</envar> is an environment variable. You must set it
|
||||
on the commandline or in your dot files (~/.profile).</para>
|
||||
on the command line or in your dot files (~/.profile).</para>
|
||||
|
||||
<para><makevar>WEB_ONLY</makevar>, <makevar>ENGLISH_ONLY</makevar> and
|
||||
<makevar>NOPORTSCVS</makevar> are makefile variables. You can set the
|
||||
variables in <filename>/etc/make.conf</filename>,
|
||||
<filename>Makefile.inc</filename> or as environment variables on the
|
||||
commandline or in your dot files.</para>
|
||||
command line or in your dot files.</para>
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
||||
|
|
|
@ -27,7 +27,7 @@
|
|||
ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE
|
||||
POSSIBILITY OF SUCH DAMAGE.
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/fdp-primer/tools/chapter.sgml,v 1.13 2001/06/22 10:29:03 nik Exp $
|
||||
$FreeBSD$
|
||||
-->
|
||||
|
||||
<chapter id="tools">
|
||||
|
@ -173,8 +173,8 @@
|
|||
<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>
|
||||
characters in the 'Latin' character set (accents, diacriticals,
|
||||
and so on), and Greek symbols.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
|
|
@ -55,7 +55,7 @@
|
|||
|
||||
<listitem>
|
||||
<para>In a list of items within a paragraph, separate each item from
|
||||
the others with a comma. Seperate the last item from the others with
|
||||
the others with a comma. Separate the last item from the others with
|
||||
a comma and the word <quote>and</quote>.</para>
|
||||
|
||||
<para>For example, look at the following:</para>
|
||||
|
|
Loading…
Reference in a new issue