some of the content was long-since decommissioned and is to be set aside into
a 'todelete' directory
some belongs properly in the archive
add the stuff from the refs directory
several minor spelling and language fixes
prefixed one command with $HOME (based on assumption)
added line-breaking to one verbose mount output example
clarifying allusion to Bob and Alice in file-transfer section
adjusting five section titles to help with "directionality"
Hello Martin,
I've been lurking on the discuss list and have fixed the text following some
suggestions I received.
Please find attached the final version of my proposed Howto; I hope it's going
to be accepted.
All the best,
Guido =8-)
This version should not be present here.....if the LFS folk wish to contribute
it, then, it should go right on top of the older version. I did not want to
make that choice for them, but having the duplicate here is also not good, so
I'm removing it.
added a DocBook 5.0 declaration and, after failing validation with jing,
changed the anchor location to be inside the <firstname/> element.
Validates now!
(and restoring commit 78ec6080e6 which
suppresses the dbhtml PI for document naming)
Assembly-HOWTO.xml was written as a DocBook 5.0 document, however it sported a
declaration of a DocBook XML 4.5 document. This confused me and I changed all
of the <xlink:href/> elements to <ulink/> elements.
reverts commit 13943cb7fb
It is not valid to have <indexterm/> elements directly as a child of a
<varlistentry/>, so I have moved them inside the <listitem/>. I tried putting
them inbetween <varlistentry/> elements (no good).
It is not valid to have <indexterm/> elements directly as a child of a
<varlistentry/>, so I have moved them inside the <listitem/>. I tried putting
them inbetween <varlistentry/> elements (no good).
It is not valid to have <indexterm/> elements directly as a child of a
<varlistentry/>, so I have moved them inside the <listitem/>. I tried putting
them inbetween <varlistentry/> elements (no good).
there were two locations where CDATA was outside of an enclosing </para> or
inside another element that could not contain it (according to the DocBook XML
element nesting model).
an <indexterm/> cannot be a direct child of an <abstract/>, so I moved it
inside of the <para/>
neither can <command/> be the direct children of a <sect1/>, so I moved them,
each inside a <para/>
An <abstract/> element can contain a <para/>, which can contain an
<itemizedlist/>, but the <itemizedlist/> may not be a direct child of an
<abstract/>.
there was a mismatch between the root element and the doctype declaration;
assuming that the root element is correct, synchronizing these two changes
fixed the validation problems