There was a bare ampersand in a <title/>, replaced with &
Quite a few <programlisting/> elements also contained bare ampersands, so
each <programlisting/> earned a child element of <![CDATA[]]>
One <parameter/> element lacked quotations on the value for its
class attribute. Corrected.
xsltproc and friends will happily generate the index in one
pass, obviating the need for the separate index.xml file, which
must be generated using the jade toolchain; thus commenting out
the (missing) external index and generating it on the fly;
N.B. there were only two </indexterm> entries in the document, but
at least they were present
The additional programs and content were stored in a directory called
ncurses_programs and were referred to in the document--the problem is that
only ./images/ were copied to the output tree, so HTML versions of the
document would fail in building AND the files would not be viewable.
Adjusted that be creating a ./resources/ directory along the same line
as the ./images/ directory. This can be changed, if desired, but this
allows for automated publication of the document. (Side benefit: this is
generalizable to all other TLDP documents.)
When generating a book (or article) index, the filename is index.sgml. Not an
issue with DocBook XML, only with the older tools which make several passes
over the input sources to create the index data (output as SGML in a file
called index.sgml) and then incorporate that into the final document.
removing extraneous and empty <author/>, non-validating <toc/>
replacing an <ulink/> with a mailto: with an <email/> element
stuffing an & in the url="" attribute value for a <ulink/>
document now validates
Though it is legal to define parameter entity substitutions in a
DTD's internal subset, you cannot actually use them there. It is only
legal to use a parameter entity substitution in an external subset.
See this:
https://www.w3.org/TR/1998/REC-xml-19980210#wfc-PEinInternalSubset
Therefore, for the XML-RPC-HOWTO, the %GoodStyleSheets; definition is
left uncommented, but the suppression of the alternate definition of
legal.notice is commented out.
Document validates and processes correctly, now, using the legal.notice
definition intended. N.B., there is no actual difference in the license
specified, just the markup used to communicate it.
The <emphasis/> tag cannot live inside a <systemitem/> or a <literal/>, but
it can certainly surround these elements; inverting to allow for validation
and processing.
first line of fdl.xml with XML text declaration was confusing xsltproc;
removed and things were fine, also removed commented out DOCTYPE declaration
used URI for DocBook 4.1.2 in system identifier in rpmupgrade.xml
commented out <xref endterm="xrefdemo" linked="xrefdemo" /> which was causing
a recursion error in the DocBook XSLT layer
document now validates and builds (except for PDF)
files were declared with <?xml version="1.0" encoding="UTF-8"?>
but were definitely not UTF-8; corrected and added Unicode BOM
Linux-Networking.xml: fixed a doubly-closed </ulink>
Overview.xml: there were several large pasted sections of text which
contained characters understood to be markup; wrapped the entire
sections in <![CDATA[ ]]> blocks;
Protocols-Standards-Services.xml: closing </sect1> tags cannot have id="" on
them: removed these; wrapped several email addresses with <email/> to allow
validation; fixed tons of URLs with proper <ulink/> elements; wrapped a few
pasted sections in <![CDATA[ ]]> blocks;
jade processor was very unhappy to have closing tags on <imagedata>;
removing them (which felt like violence) allowed the document to be
validated and processed
In his document build system, each script is cooked (wrapped in <![ CDATA []]>
during build process--this is elegant, but we are not calling his build
Makefile, so we need to store the cooked scripts in the source tree.
Martin A. Brown