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
the doctype declaration had conflicting entries; the public identifier said
4.1.2 and the system identifier said 4.0; I would not have noticed this,
except that xmllint was complaining about the <author/> element containing an
<email/> (invalid!)
this was easily resolved by changing the version of this document to be a
DocBook XML 4.2 document
DocBook 4.x appears to be fairly picky about order in <author/> elements and
the document will not validate without the order being correct. Fixed.
Also, in the <revhistory/>, there were plenty of places where multiple
<revremark/> elements needed to be wrapped in a <revdescription/> along with a
bunch of <remark/> elements instead.
first, this is not XSL and in DocBook 4.x, these extra namespaces confuse the
processing toolchain (may be different in DocBook 5.x); next, xmllint refuses
to validate the document because of the order of elements in, for example the
<author/> elements and the <affiliation/> elements; just flipping these in
most cases did the trick
added a bunch of corrections for <itemizedlist/> <listitem/> and <para/>
nesting to match the DocBook content model more strictly; this allows full
validation of the document
the external general entities (files) which were getting pulled in already
contained a <programlisting/> element; this XML element was not necessary, but
the lack of an <areaspec/> inside the <programlistingco/> was giving xmllint
fits.
apparently, DocBook is quite picky about the order of children elements within
the <affiliation/> element; so rearranged; and also only one of <revremark/>
or <revdescription/> is (technically) allowed in a <revision/>, so I chose to
convert the <revremark/> elements to <remark/> and drop them inside of a
<revdescription/>, which allows much richer expression of content
I don't know how this document ever validated before. There were countless
locations where there were extra </itemize> closing tags and tons of missing
<itemize> opening tags.
I tried not to do any violence to the nesting, but it was very difficult to
understand, given the ambiguity. The document now validates and can be built.
the entire set of directories here had been checked in (in 2005) under
NCURSES-Programming-HOWTO; and has since been moved to a subdirectory,
NCURSES-Programming-HOWTO/resources
this is cruft and does not need to be here (there are even newer files in the
NCURSES-Programming-HOWTO/resources/ncurses_programs directory
From: Rick Moen <rick@linuxmafia.com>
To: discuss@en.tldp.org
Subject: Linux User Group HOWTO v. 1.8.5 ready
Date: Thu, 25 Feb 2016 04:30:58
Good folks, I have a major revamp of HOWTO ready for the submission
process.
http://linuxmafia.com/lug/User-Group-HOWTO.sgml
This is Linuxdoc SGML, selected by original author Kendall Grant Clark
back in 1997. I've verified clean parsing of this revision.
HTML output here: http://linuxmafia.com/lug/User-Group-HOWTO.html
Licence has been modified slightly on this release from the prior
CC BY-SA 3.0, to CC BY-SA 4.0 (current revision). CC BY-SA is listed as
an accepted licence on http://wiki.tldp.org/LdpWikiDefaultLicence ,
and I doubt the revamped licence text would create any problme. (If
LDP has a problem with 4.0, I will back-rev that.)
I hope someone will do me the courtesy of picking up the SGML file and
feeding it into GitHub. Please advise. Thank you!
--
Cheers, QA engineer walks into a bar. Orders a beer.
Rick Moen Orders 0 beers. Orders 999999999 beers. Orders
rick@linuxmafia.com a lizard. Orders -1 beers. Orders a sfdeljknesv.
McQ! (4x80) -- @sempf, https://www.sempf.net/post/On-Testing1.aspx
Several <xref/> elements used the endterm attribute, which takes the entire
content contained in the element as replacement. Because the endterm was
also, for example, a <section/>, the replaced text was a gigantic (multi-page)
link with the whole section included. Unintended, I'm sure.
Move the <?dbhtml filename="glossary"?> to its correct location after the
opening <glossary> tag; otherwise the index.html file gets named
glossary.html (oops!).
fop.extensions are no longer supported, deprecated
fop1.extensions are required when handling some of our documents
which contain all sorts of features; citations for choices are in the XSL
shade.verbatim is just to make FOP output look more like other LDP PDFs
added a reference to bufferbloat
upgraded a few untagged text items to be wrapped with <command>, a few others
from <command> to the more appropriate <emphasis> or <constant>
added a FIXME for more description on enqueuing from userspace/network