mirror of https://github.com/tLDP/LDP
updated
This commit is contained in:
gferg
parent
426175a720
commit
c9570c1fd6
|
|
@ -3,6 +3,7 @@
|
|||
"http://docbook.org/xml/4.1.2/docbookx.dtd" [
|
||||
<!ENTITY howto "http://tldp.org/HOWTO/">
|
||||
<!ENTITY mini-howto "http://tldp.org/HOWTO/mini/">
|
||||
<!ENTITY home "http://www.catb.org/~esr/">
|
||||
]>
|
||||
|
||||
<article>
|
||||
|
|
@ -20,11 +21,28 @@
|
|||
</author>
|
||||
|
||||
<revhistory>
|
||||
<revision>
|
||||
<revnumber>v1.3</revnumber>
|
||||
<date>2004-02-27</date>
|
||||
<authorinitials>esr</authorinitials>
|
||||
<revremark>
|
||||
Add pointers to two editors.
|
||||
</revremark>
|
||||
</revision>
|
||||
<revision>
|
||||
<revnumber>v1.2</revnumber>
|
||||
<date>2003-02-17</date>
|
||||
<authorinitials>esr</authorinitials>
|
||||
<revremark>
|
||||
Reorder to defer references to SGML until after it has been
|
||||
introduced.
|
||||
</revremark>
|
||||
</revision>
|
||||
<revision>
|
||||
<revnumber>v1.1</revnumber>
|
||||
<date>2002-10-01</date>
|
||||
<authorinitials>esr</authorinitials>
|
||||
<revremark>
|
||||
<revremark>
|
||||
Correct inadvertent misrepresentation of FSF's position.
|
||||
Added pointer to the DocBook FAQ.
|
||||
</revremark>
|
||||
|
|
@ -57,17 +75,15 @@ including the Linux kernel, GNOME, KDE, Samba, and the Linux
|
|||
Documentation Project. The advocates of XML-based "structural markup"
|
||||
(as opposed to the older style of "presentation markup" exemplified by
|
||||
troff, Tex, and Texinfo) seem to have won the theoretical
|
||||
battle.</para>
|
||||
battle. You can generate presentation markup from structural markup,
|
||||
but going in the other direction is very difficult.</para>
|
||||
|
||||
<para>Nevertheless, a lot of confusion surrounds DocBook and the
|
||||
programs that support it. Its devotees speak an argot that is dense
|
||||
and forbidding even by computer-science standards, slinging around
|
||||
acronyms that have no obvious relationship to the things you need to
|
||||
do to write markup and make HTML or Postscript from it. XML standards
|
||||
and technical papers are notoriously obscure. Most DocBook-related
|
||||
tools are very poorly documented, and their documentation is
|
||||
especially prone to assume way too much prior knowledge on the
|
||||
reader's part.</para>
|
||||
and technical papers are notoriously obscure.</para>
|
||||
|
||||
<para>This HOWTO will attempt to clear up the major mysteries
|
||||
surrounding DocBook and its application to open-source documentation
|
||||
|
|
@ -98,13 +114,13 @@ system is one rich, searchable, cross-indexed and hyperlinked
|
|||
database (rather than being scattered across several different formats
|
||||
in multiple locations as it is now).</para>
|
||||
|
||||
<para>Ideally, whenever you install a software package on your machine
|
||||
<para>Ideally, whenever you install a software package on your machine
|
||||
it would register its DocBook documentation into your system's
|
||||
catalog. HTML, properly indexed and cross-linked to the HTML in the
|
||||
catalog. HTML, properly indexed and cross-linked to the HTML in the
|
||||
rest of your catalog, would be generated. The new package's
|
||||
documentation would then be available through your browser. All
|
||||
your documentation would would be searchable through an interface
|
||||
resembling a good Web search engine.</para>
|
||||
documentation would then be available through your browser. All your
|
||||
documentation would be searchable through an interface resembling a
|
||||
good Web search engine.</para>
|
||||
|
||||
<para>HTML itself is not quite rich enough a format to get us to that
|
||||
world. To name just one lack, you can't explicitly declare index
|
||||
|
|
@ -116,10 +132,11 @@ that's why so many projects are adopting it.</para>
|
|||
find it unpleasantly heavyweight, and too verbose to be really
|
||||
comfortable as a composition format. That's OK; as long as the markup
|
||||
tools they like (things like Perl POD or GNU Texinfo) can generate
|
||||
DocBook out their back ends, we can all still get we want. It doesn't
|
||||
matter whether or not everybody writes in DocBook — as long as
|
||||
it becomes the common document interchange format that everyone uses,
|
||||
we'll still get unified searchable documentation databases.</para>
|
||||
DocBook out their back ends, we can all still get what we want. It
|
||||
doesn't matter whether or not everybody writes in DocBook — as
|
||||
long as it becomes the common document interchange format that
|
||||
everyone uses, we'll still get unified searchable documentation
|
||||
databases.</para>
|
||||
|
||||
</sect1>
|
||||
<sect1><title>Structural markup: a primer</title>
|
||||
|
|
@ -174,7 +191,7 @@ instructions to your formatter.</para>
|
|||
final document would be controlled by a <firstterm>stylesheet</firstterm>
|
||||
<indexterm><primary>stylesheet</primary></indexterm>. It is the
|
||||
stylesheet that would tell the formatter "render emphasis as a font
|
||||
change to boldface". One advantage of presentation-markup languages
|
||||
change to boldface". One advantage of structural-markup languages
|
||||
is that by changing a stylesheet you can globally change the
|
||||
presentation of the document (to use different fonts, for example)
|
||||
without having to hack all the the individual instances of (say)
|
||||
|
|
@ -185,8 +202,8 @@ without having to hack all the the individual instances of (say)
|
|||
|
||||
<para>(Note: to keep the explanation simple, most of this
|
||||
section is going to tell some lies, mainly by omitting a lot of
|
||||
history. Truthfulness will be fully restored in a following
|
||||
section.)</para>
|
||||
history. Truthfulness will be fully restored in a
|
||||
<link linkend="sgml">following section</link>.)</para>
|
||||
|
||||
<para>DocBook is a structural-level markup language. Specifically, it
|
||||
is a dialect of XML. A DocBook document is a hunk of XML that uses
|
||||
|
|
@ -215,7 +232,7 @@ first step is to pass it through a validating parser (the front end of
|
|||
the DocBook formatter). This program checks your document against the
|
||||
DocBook DTD to make sure you aren't breaking any of the DTD's
|
||||
structural rules (otherwise the back end of the formatter, the part
|
||||
that applies your style sheet, might become quite confused)</para>
|
||||
that applies your style sheet, might become quite confused).</para>
|
||||
|
||||
<para>The validating parser will either bomb out, giving you error
|
||||
messages about places where the document structure is broken, or translate
|
||||
|
|
@ -262,12 +279,16 @@ there.</para>
|
|||
</sect1>
|
||||
<sect1><title>The DocBook toolchain</title>
|
||||
|
||||
<para>The easiest way to format and render XML-DocBook documents is to
|
||||
use the <application>xmlto</application> toolchain. This ships with
|
||||
Red Hat; Debian users can get it with the command <command>apt-get
|
||||
install xmlto</command>.</para>
|
||||
|
||||
<para>Normally, what you'll do to make XHTML from your
|
||||
DocBook sources will look like this:</para>
|
||||
|
||||
<screen>
|
||||
bash$ xmlto xhtml foo.xml
|
||||
Convert to XHTML
|
||||
bash$ ls *.html
|
||||
ar01s02.html ar01s03.html ar01s04.html index.html
|
||||
</screen>
|
||||
|
|
@ -278,7 +299,6 @@ index page and two parts. Making one big page is just as easy:</para>
|
|||
|
||||
<screen>
|
||||
bash$ xmlto xhtml-nochunks foo.xml
|
||||
Convert to XHTML
|
||||
bash$ ls *.html
|
||||
foo.html
|
||||
</screen>
|
||||
|
|
@ -287,14 +307,13 @@ foo.html
|
|||
|
||||
<screen>
|
||||
bash$ xmlto ps foo.xml # To make Postscript
|
||||
Convert to XSL-FO
|
||||
Making portrait pages on A4 paper (210mmx297mm)
|
||||
Post-process XSL-FO to DVI
|
||||
Post-process DVI to PS
|
||||
bash$ ls *.ps
|
||||
foo.ps
|
||||
</screen>
|
||||
|
||||
<para>Some older versions of <command>xmlto</command> may be
|
||||
more verbose, emitting noise like "Coverting to XHTML" and so forth.</para>
|
||||
|
||||
<para>To turn your documents into HTML or Postscript, you need an
|
||||
engine that can apply the combination of DocBook DTD and
|
||||
a suitable stylesheet to your document. Here is how the
|
||||
|
|
@ -302,18 +321,21 @@ open-source tools for doing this fit together:</para>
|
|||
|
||||
<mediaobject>
|
||||
<imageobject> <imagedata fileref="figure2.png" format="PNG"/></imageobject>
|
||||
<caption>
|
||||
<para>Present-day XML-DocBook toolchain</para>
|
||||
</caption>
|
||||
</mediaobject>
|
||||
|
||||
<para>Parsing your document and applying the stylesheet transformation
|
||||
will be handled by one of three programs. The most likely one is
|
||||
<application>xsltproc</application><indexterm><primary>xsltproc</primary></indexterm>,
|
||||
the parser that ships with Red Hat 7.3. The other possibilities are
|
||||
two Java programs,
|
||||
the parser that ships with Red Hat 7.3 and later versions. The other
|
||||
possibilities are two Java programs,
|
||||
<application>Saxon</application><indexterm><primary>Saxon</primary></indexterm>
|
||||
and
|
||||
<application>Xalan</application><indexterm><primary>Xalan</primary></indexterm>,</para>
|
||||
|
||||
<para>It is relatively easy to generate high-quality XHTML from either
|
||||
<para>It is relatively easy to generate high-quality XHTML from
|
||||
DocBook; the fact that XHTML is simply another XML DTD helps a lot.
|
||||
Translation to HTML is done by applying a rather simple stylesheet,
|
||||
and that's the end of the story. RTF is also simple to generate in
|
||||
|
|
@ -322,9 +344,9 @@ text approximation in a pinch.</para>
|
|||
|
||||
<para>The awkward case is print. Generating high-quality printed
|
||||
output (which means, in practice, Adobe's
|
||||
PDF<indexterm><primary>PDF</primary></indexterm>
|
||||
(Portable Document Format) is difficult. Doing it right requires
|
||||
algorithmically duplicating the delicate judgments of a human
|
||||
PDF<indexterm><primary>PDF</primary></indexterm> or Portable Document
|
||||
Format, a packaged form of PostScript) is difficult. Doing it right
|
||||
requires algorithmically duplicating the delicate judgments of a human
|
||||
typesetter moving from content to presentation level.</para>
|
||||
|
||||
<para>So, first, a stylesheet translates Docbook's structural markup
|
||||
|
|
@ -369,14 +391,17 @@ with rough edges and missing features.</para>
|
|||
|
||||
<mediaobject>
|
||||
<imageobject> <imagedata fileref="figure3.png" format="PNG"/></imageobject>
|
||||
<caption>
|
||||
<para>Future XML-DocBook toolchain with FOP.</para>
|
||||
</caption>
|
||||
</mediaobject>
|
||||
|
||||
<para>FOP has competition. There is another project called
|
||||
<application>xsl-fo-proc</application><indexterm><primary>xsl-fo-proc</primary></indexterm>
|
||||
which aims to do the same things as FOP, but in C++ (and therefore
|
||||
both faster than Java and not relying on the Java environment). As of
|
||||
August 2002 FOP is in an unfinished alpha state, not as far along as
|
||||
FOP.</para>
|
||||
August 2002 <application>xsl-fo-proc</application> is in an unfinished
|
||||
alpha state, not as far along as FOP.</para>
|
||||
|
||||
</sect1>
|
||||
<sect1><title>Who are the projects and the players?</title>
|
||||
|
|
@ -385,24 +410,9 @@ FOP.</para>
|
|||
Committee, headed by Norman Walsh. Norm is the principal author of
|
||||
the DocBook stylesheets, a man who has focused remarkable energy and
|
||||
talent over many years on the extremely complex problems DocBook
|
||||
addresses. He is as universally respected in the DocBook/SGML/XML
|
||||
addresses. He is as universally respected in the DocBook
|
||||
community as Linus Torvalds is in the Linux world.</para>
|
||||
|
||||
<para>The <ulink url="http://sources.redhat.com/docbook-tools/">
|
||||
docbook-tools</ulink> project provides open-source tools for
|
||||
converting SGML DocBook to HTML, Postscript, and other formats. This
|
||||
package is shipped with Red Hat and other Linux distributions. It is
|
||||
maintained by Mark Galassi.</para>
|
||||
|
||||
<para><ulink url="http://www.jclark.com/jade/">Jade</ulink> is an
|
||||
engine used to apply DSSSL stylesheets to SGML documents. It is
|
||||
maintained by James Clark.</para>
|
||||
|
||||
<para><ulink url="http://openjade.sourceforge.net/">OpenJade</ulink>
|
||||
is a community project undertaken because the founders thought James
|
||||
Clark's maintainance of Jade was spotty. The docbook-tools programs
|
||||
use OpenJade.</para>
|
||||
|
||||
<para><ulink url="http://xmlsoft.org/XSLT/">libxslt</ulink> is a C
|
||||
library that interprets XSLT, applying stylesheets to XML documents.
|
||||
It includes a wrapper program, <command>xsltproc</command>, that can be
|
||||
|
|
@ -421,14 +431,6 @@ programs that interpret XSLT. Saxon seems to be designed to work
|
|||
under Windows. Xalan is part of the XML Apache project and native to
|
||||
Linux and BSD; it's designed to work with FOP.</para>
|
||||
|
||||
<para><ulink
|
||||
url="http://users.ox.ac.uk/~rahtz/passivetex/">PassiveTeX</ulink> the
|
||||
package of LaTeX macros that <application>xmlto</application> uses for
|
||||
producing DVI from XML-DocBook. <ulink
|
||||
url="http://jadetex.sourceforge.net/">JadeTex</ulink> is the package
|
||||
of LaTeX macros that OpenJade uses for producing DVI from
|
||||
SGML-DocBook.</para>
|
||||
|
||||
<para><ulink url="http://xml.apache.org/fop/">FOP</ulink> translates
|
||||
XML Formatting Objects to PDF. It is part of the Apache XML project
|
||||
and is designed to work with Xalan.</para>
|
||||
|
|
@ -438,9 +440,9 @@ and is designed to work with Xalan.</para>
|
|||
|
||||
<para>The second biggest problem with DocBook is the effort needed to
|
||||
convert old-style presentation markup to DocBook markup. Human beings
|
||||
can usually parse the presentatition of a document into logical
|
||||
can usually parse the presentation of a document into logical
|
||||
structure automatically, because (for example) they can tell from
|
||||
context when an italic font means `emphasis' and when it meabs
|
||||
context when an italic font means `emphasis' and when it means
|
||||
something else such as `this is a foreign phrase'.</para>
|
||||
|
||||
<para>Somehow, in converting documents to DocBook, those
|
||||
|
|
@ -460,9 +462,10 @@ various other formats:</para>
|
|||
support DocBook as an interchange format. Texinfo has enough
|
||||
structure to make reasonably good automatic conversion possible, and
|
||||
the 4.x versions of <command>makeinfo</command> feature a
|
||||
<option>--docbook</option> switch that generates DocBook. More at the
|
||||
<ulink url="http://www.gnu.org/directory/texinfo.html">makeinfo
|
||||
project page</ulink>.</para>
|
||||
<option>--docbook</option> switch that generates DocBook.
|
||||
More at the <ulink
|
||||
url="http://www.gnu.org/directory/texinfo.html">makeinfo project
|
||||
page</ulink>.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
|
@ -472,7 +475,7 @@ project page</ulink>.</para>
|
|||
<para>There is a <ulink
|
||||
url="http://www.cpan.org/modules/by-module/Pod/">POD::DocBook</ulink>
|
||||
module that translates Plain Old Documentation markup to DocBook. It
|
||||
claims to support every DocBook tag except the L<> italic tag.
|
||||
claims to translate every POD tag except the L<> italic tag.
|
||||
The man page also says "Nested =over/=back lists are not supported
|
||||
within DocBook." but notes that the module has been heavily
|
||||
tested.</para>
|
||||
|
|
@ -507,7 +510,7 @@ features for automatic translation to get some traction.</para>
|
|||
<para>I wrote a tool to do this myself, because I couldn't find
|
||||
anything else that did a half-decent job of it (and the problem is
|
||||
interesting). It's called <ulink
|
||||
url="http://www.tuxedo.org/~esr/doclifter/">doclifter</ulink>. It will
|
||||
url="&home;/doclifter/">doclifter</ulink>. It will
|
||||
translate to either SGML or XML DocBook from
|
||||
<citerefentry><refentrytitle>man</refentrytitle>
|
||||
<manvolnum>7</manvolnum></citerefentry>,
|
||||
|
|
@ -528,6 +531,15 @@ for details.</para>
|
|||
<para>One thing we presently do not have is a good open-source
|
||||
structure editor for SGML/XML documents.</para>
|
||||
|
||||
<para>The <ulink url='http://conglomerate.org/'>Conglomerate</ulink> project
|
||||
aims specifically at producing a good DocBook editor. As of early
|
||||
2004 it is stilll alpha software.</para>
|
||||
|
||||
<para>The <ulink
|
||||
url='http://www.freespiders.org/projects/gmlview/'>MlView</ulink>
|
||||
project is an XML editor, not specifically DocBook targeted. As of
|
||||
early 2004 it lacks documentation and appears to be in alpha.</para>
|
||||
|
||||
<para><ulink url="http://www.lyx.org/">LyX</ulink> is a GUI word processor
|
||||
that uses LaTeX for printing and supports structural editing of LaTeX
|
||||
markup. There is a LaTeX package that generates DocBook, and a
|
||||
|
|
@ -550,11 +562,21 @@ the future, but it's not there yet.</para>
|
|||
|
||||
<para><ulink url="http://www.freesoftware.fsf.org/thotbook/">ThotBook</ulink>
|
||||
is a project to put together a GUI editor for DocBook based on
|
||||
the Thot toolkit. It way be moribund; the web page was not updated
|
||||
the Thot toolkit. It may be moribund; the web page was not updated
|
||||
from November 2001 to August 2002 (time of writing).</para>
|
||||
|
||||
<para>Most people still hack the tags by hand using either vi or Emacs, using
|
||||
psgml to validate the results.</para>
|
||||
<para>Most people still hack the tags by hand using either vi or emacs.</para>
|
||||
|
||||
</sect1>
|
||||
<sect1><title>Hints and tricks</title>
|
||||
|
||||
<para>It is possible to generate an index by including an empty
|
||||
<index/> tag at the point in your document where you wish
|
||||
it to appear. Be warned that, as of early 2004, this facility is
|
||||
still somewhat primitive. It won't merge ranges, and the output
|
||||
generated for PostScript is not yet production-quality.</para>
|
||||
|
||||
<para>This space is reserved for more hints and tricks.</para>
|
||||
|
||||
</sect1>
|
||||
<sect1><title>Related standards and practices</title>
|
||||
|
|
@ -570,18 +592,18 @@ cataloguing and metadata.</para>
|
|||
url="http://scrollkeeper.sourceforge.net/">Scrollkeeper</ulink>
|
||||
project aims directly to meet this need. It provides a simple set of
|
||||
script hooks that can be used by package install and uninstall
|
||||
productions to register and unregister their documentation.</para>
|
||||
productions to register and unregister their documentation into and
|
||||
out of a shared, searchable system-wide database.</para>
|
||||
|
||||
<para>Scrollkeeper uses the <ulink
|
||||
url="http://www.ibiblio.org/osrt/omf/"> Open Metadata Format</ulink>.
|
||||
url="http://www.ibiblio.org/osrt/omf/">Open Metadata Format</ulink>.
|
||||
This is a standard for indexing open-source documentation analogous to
|
||||
a library card-catalog system. The idea is to support rich search
|
||||
facilities that use the card-catalog metadata as well as the source
|
||||
text of the documentation itself.</para>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1><title>SGML and SGML-Tools</title>
|
||||
<sect1 id="sgml"><title>SGML and SGML-Tools</title>
|
||||
|
||||
<para>In previous sections, I have thrown away a lot of DocBook's
|
||||
history. XML has an older brother,
|
||||
|
|
@ -591,10 +613,11 @@ Markup Language.</para>
|
|||
<para>Until mid-2002, no discussion of DocBook would have been
|
||||
complete without a long excursion into SGML, the differences between
|
||||
SGML and XML, and detailed descriptions of the SGML DocBook toolchain.
|
||||
Life can be simpler now; a XML DocBook toolchain is available in open
|
||||
source, works as well as the SGML toolchain ever did, and is easier to
|
||||
use, If you don't think you'll ever have to deal with old SGML-Docbook
|
||||
documents, you can skip the remainder of this section.</para>
|
||||
Life can be simpler now; an XML DocBook toolchain is available in open
|
||||
source, works as well as the SGML toolchain ever did, and is much
|
||||
easier to use. If you don't think you'll ever have to deal with old
|
||||
SGML-Docbook documents, you can skip the remainder of this
|
||||
section.</para>
|
||||
|
||||
<sect2><title>DocBook SGML</title>
|
||||
|
||||
|
|
@ -627,17 +650,42 @@ correct version:</para>
|
|||
<para>The DSSSL toolchain is what processed DocBook SGML.
|
||||
Under it, a document goes from DocBook format through one of two
|
||||
closely-related stylesheet engines called Jade and OpenJade. These
|
||||
turn it into a TeX-macro markup. which is processed by a package called
|
||||
turn it into a TeX-macro markup, which is processed by a package called
|
||||
JadeTeX, into DVIs, which then get turned into Postscript.</para>
|
||||
</sect2>
|
||||
|
||||
</sect2>
|
||||
<sect2><title>SGML tools</title>
|
||||
|
||||
<para>The <ulink url="http://sources.redhat.com/docbook-tools/">
|
||||
docbook-tools</ulink> project provides open-source tools for
|
||||
converting SGML DocBook to HTML, Postscript, and other formats. This
|
||||
package is shipped with Red Hat and other Linux distributions. It is
|
||||
maintained by Mark Galassi.</para>
|
||||
|
||||
<para><ulink url="http://www.jclark.com/jade/">Jade</ulink> is an
|
||||
engine used to apply DSSSL stylesheets to SGML documents. It is
|
||||
maintained by James Clark.</para>
|
||||
|
||||
<para><ulink url="http://openjade.sourceforge.net/">OpenJade</ulink>
|
||||
is a community project undertaken because the founders thought James
|
||||
Clark's maintainance of Jade was spotty. The docbook-tools programs
|
||||
use OpenJade.</para>
|
||||
|
||||
<para><ulink
|
||||
url="http://users.ox.ac.uk/~rahtz/passivetex/">PassiveTeX</ulink> the
|
||||
package of LaTeX macros that <application>xmlto</application> uses for
|
||||
producing DVI from XML-DocBook. <ulink
|
||||
url="http://jadetex.sourceforge.net/">JadeTex</ulink> is the package
|
||||
of LaTeX macros that OpenJade uses for producing DVI from
|
||||
SGML-DocBook.</para>
|
||||
|
||||
</sect2>
|
||||
<sect2><title>Why SGML DocBook is dead</title>
|
||||
|
||||
<para>The DSSSL toolchain is, as far as new development goes,
|
||||
effectively dead. The XSLT toolchain has just reached production
|
||||
status as I write in August 2002; a working version shipped in Red Hat
|
||||
7.3. It's where DocBook developers are putting almost all of their
|
||||
effort.</para>
|
||||
effectively dead. The XSLT toolchain has reached production status in
|
||||
mid-2002; a working version shipped in Red Hat 7.3. It's where
|
||||
DocBook developers are putting almost all of their effort.</para>
|
||||
|
||||
<para>The reason for the change to XML was threefold. First,
|
||||
SGML turned out to be too complicated to use; then, DSSSL turned out
|
||||
|
|
@ -667,10 +715,10 @@ write and modify. (It was a dialect of Scheme. Your humble editor, a
|
|||
LISP-head from way back, shakes his head in sad bemusement that
|
||||
this should drive people away.)</para>
|
||||
|
||||
<para>XML fans like to sum up all these changes with "XML: tastes great, less
|
||||
filling."</para>
|
||||
</sect2>
|
||||
<para>XML fans like to sum up all these changes with <quote>XML:
|
||||
tastes great, less filling.</quote></para>
|
||||
|
||||
</sect2>
|
||||
<sect2><title>SGML-Tools</title>
|
||||
|
||||
<para>SGML-Tools was the name of a DTD used by the <ulink
|
||||
|
|
@ -684,8 +732,8 @@ Lite</ulink> is still maintained.</para>
|
|||
|
||||
<para>The LDP has been phasing out SGML-Tools in favor of DocBook, but
|
||||
it is still possible you might take over an old HOWTO. These can be
|
||||
regognized by the identifying header "<!doctype linuxdoc
|
||||
system>. If this happens to you, convert the thing to XML DocBook
|
||||
recognized by the identifying header "<!doctype linuxdoc
|
||||
system>". If this happens to you, convert the thing to XML DocBook
|
||||
and give the old version a quick burial.</para>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
|
@ -694,7 +742,7 @@ and give the old version a quick burial.</para>
|
|||
|
||||
<para>One of the things that makes learning DocBook difficult is that
|
||||
the sites related to it tend to overwhelm the newbie with long lists
|
||||
of W3C standards, massive exercises in SGML theology, and dense
|
||||
of W3C standards, massive exercises in markup theology, and dense
|
||||
thickets of abstract terminology. We're going to try to avoid that
|
||||
here by giving you just a few selected references to look at.</para>
|
||||
|
||||
|
|
@ -729,8 +777,9 @@ url="http://vig.pearsoned.com/store/product/0,,store-562_banner-0_isbn-013642299
|
|||
XML Documents</ulink> (Prentice-Hall, ISBN: 0-13-642299-3).</para>
|
||||
|
||||
<para>For XML only, <ulink
|
||||
url="http://www.oreilly.com/catalog/xmlnut2/">XML In A Nutshell</ulink>
|
||||
by W. Scott Means and Elliotte "Rusty" Harold is very good.</para>
|
||||
url="http://www.oreilly.com/catalog/xmlnut2/">XML In A
|
||||
Nutshell</ulink> by W. Scott Means and Elliotte <quote>Rusty</quote>
|
||||
Harold is very good.</para>
|
||||
|
||||
<para><ulink url="http://www.ibiblio.org/xml/books/bible/">The XML
|
||||
Bible</ulink> looks like a pretty comprehensive reference on XML and
|
||||
|
|
|
|||
Binary file not shown.
|
Before Width: | Height: | Size: 900 B After Width: | Height: | Size: 3.1 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 3.7 KiB After Width: | Height: | Size: 3.3 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 3.1 KiB After Width: | Height: | Size: 2.7 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 7.1 KiB After Width: | Height: | Size: 7.1 KiB |
|
|
@ -1123,7 +1123,7 @@ How to become a totally "small time" DNS admin. </Para>
|
|||
DocBook-Demystification-HOWTO</ULink>,
|
||||
<CiteTitle>DocBook Demystification HOWTO</CiteTitle>
|
||||
</Para><Para>
|
||||
<CiteTitle>Updated: Oct 2002</CiteTitle>.
|
||||
<CiteTitle>Updated: Feb 2004</CiteTitle>.
|
||||
Attempts to clear the fog and mystery surrounding the DocBook markup
|
||||
system and the tools that go with it. </Para>
|
||||
</ListItem>
|
||||
|
|
@ -2058,7 +2058,7 @@ under Linux. </Para>
|
|||
K7s5a-HOWTO</ULink>,
|
||||
<CiteTitle>The Elite's K7s5a mainboard HOWTO</CiteTitle>
|
||||
</Para><Para>
|
||||
<CiteTitle>Updated: Jan 2004</CiteTitle>.
|
||||
<CiteTitle>Updated: Feb 2004</CiteTitle>.
|
||||
Describes how to use Elite's K7s5a board with Linux. </Para>
|
||||
</ListItem>
|
||||
|
||||
|
|
@ -2309,7 +2309,7 @@ This HOWTO has been removed for review. </Para>
|
|||
Linksys-Blue-Box-Router-HOWTO</ULink>,
|
||||
<CiteTitle>Linksys Blue Box Router HOWTO</CiteTitle>
|
||||
</Para><Para>
|
||||
<CiteTitle>Updated: Jul 2003</CiteTitle>.
|
||||
<CiteTitle>Updated: Feb 2004</CiteTitle>.
|
||||
Hints and tips for managing Linksys
|
||||
routers from a Linux system, including the firmware upgrade procedure. </Para>
|
||||
</ListItem>
|
||||
|
|
|
|||
|
|
@ -475,7 +475,7 @@ This HOWTO has been removed for review. </Para>
|
|||
K7s5a-HOWTO</ULink>,
|
||||
<CiteTitle>The Elite's K7s5a mainboard HOWTO</CiteTitle>
|
||||
</Para><Para>
|
||||
<CiteTitle>Updated: Jan 2004</CiteTitle>.
|
||||
<CiteTitle>Updated: Feb 2004</CiteTitle>.
|
||||
Describes how to use Elite's K7s5a board with Linux. </Para>
|
||||
</ListItem>
|
||||
|
||||
|
|
@ -1148,7 +1148,7 @@ scanner device on a system running Linux. </Para>
|
|||
Linksys-Blue-Box-Router-HOWTO</ULink>,
|
||||
<CiteTitle>Linksys Blue Box Router HOWTO</CiteTitle>
|
||||
</Para><Para>
|
||||
<CiteTitle>Updated: Jul 2003</CiteTitle>.
|
||||
<CiteTitle>Updated: Feb 2004</CiteTitle>.
|
||||
Hints and tips for managing Linksys
|
||||
routers from a Linux system, including the firmware upgrade procedure. </Para>
|
||||
</ListItem>
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ Topics covered in this section include:
|
|||
DocBook-Demystification-HOWTO</ULink>,
|
||||
<CiteTitle>DocBook Demystification HOWTO</CiteTitle>
|
||||
</Para><Para>
|
||||
<CiteTitle>Updated: Oct 2002</CiteTitle>.
|
||||
<CiteTitle>Updated: Feb 2004</CiteTitle>.
|
||||
Attempts to clear the fog and mystery surrounding the DocBook markup
|
||||
system and the tools that go with it. </Para>
|
||||
</ListItem>
|
||||
|
|
|
|||
|
|
@ -984,7 +984,7 @@ How to enable the Linux IP Masquerade feature on a given Linux host. </Para>
|
|||
Linksys-Blue-Box-Router-HOWTO</ULink>,
|
||||
<CiteTitle>Linksys Blue Box Router HOWTO</CiteTitle>
|
||||
</Para><Para>
|
||||
<CiteTitle>Updated: Jul 2003</CiteTitle>.
|
||||
<CiteTitle>Updated: Feb 2004</CiteTitle>.
|
||||
Hints and tips for managing Linksys
|
||||
routers from a Linux system, including the firmware upgrade procedure. </Para>
|
||||
</ListItem>
|
||||
|
|
|
|||
|
|
@ -1,34 +1,3 @@
|
|||
From esr@snark.thyrsus.com Thu Feb 26 20:42:49 2004
|
||||
Received: by mail01.powweb.com (mbox 1061.gferg) (with Cubic Circle's
|
||||
cucipop (v1.31 1998/05/13) Fri Feb 27 06:24:22 2004)
|
||||
X-From_: submit-return-7753-gferg=fergusontechgroup.com@en.tldp.org Thu
|
||||
Feb 26 17:50:17 2004
|
||||
Return-Path: <submit-return-7753-gferg=fergusontechgroup.com@en.tldp.org>
|
||||
X-Original-To: gferg@fergusontechgroup.com
|
||||
Delivered-To: 1061.gferg@mail01.powweb.com
|
||||
Received: from gabber.metalab.unc.edu (gabber.metalab.unc.edu
|
||||
[152.2.241.57]) by mail01.powweb.com (Postfix) with SMTP id 9F5D136A38 for
|
||||
<gferg@fergusontechgroup.com>; Thu, 26 Feb 2004 17:50:16 -0800 (PST)
|
||||
Received: (qmail 31923 invoked by uid 1008); 27 Feb 2004 01:50:16 -0000
|
||||
Mailing-List: contact submit-help@en.tldp.org; run by ezmlm
|
||||
Precedence: bulk
|
||||
X-No-Archive: yes
|
||||
List-Post: <mailto:submit@en.tldp.org>
|
||||
List-Help: <mailto:submit-help@en.tldp.org>
|
||||
List-Unsubscribe:
|
||||
<mailto:submit-unsubscribe-gferg=fergusontechgroup.com@en.tldp.org>
|
||||
List-Subscribe: <mailto:submit-subscribe@en.tldp.org>
|
||||
Delivered-To: mailing list submit@en.tldp.org
|
||||
Received: (qmail 31915 invoked from network); 27 Feb 2004 01:50:15 -0000
|
||||
Date: Thu, 26 Feb 2004 20:42:49 -0500
|
||||
From: "Eric S. Raymond" <esr@snark.thyrsus.com>
|
||||
Message-Id: <200402270142.i1R1gnWK029547@snark.thyrsus.com>
|
||||
To: submit@en.tldp.org
|
||||
Subject: Linksys Blue Box Router HOWTO update
|
||||
X-Evolution-Source: pop://1061.gferg@mail.fergusontechgroup.com
|
||||
Mime-Version: 1.0
|
||||
Content-Transfer-Encoding: 8bit
|
||||
|
||||
<?xml version="1.0"?>
|
||||
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
|
||||
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [
|
||||
|
|
@ -517,17 +486,3 @@ from August of 2000.</para>
|
|||
</sect1>
|
||||
</article>
|
||||
|
||||
<!--
|
||||
The following sets edit modes for GNU EMACS
|
||||
Local Variables:
|
||||
fill-column:75
|
||||
compile-command: "mail -s \"Linksys Blue Box Router HOWTO update\" submit@en.tldp.org <Linksys-Blue-Box-Router-HOWTO.xml"
|
||||
End:
|
||||
End:
|
||||
-->
|
||||
|
||||
|
||||
---------------------------------------------------------------------
|
||||
To unsubscribe, e-mail: submit-unsubscribe@en.tldp.org
|
||||
For additional commands, e-mail: submit-help@en.tldp.org
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue