Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DocBook 5.0 validation nits #3

Open
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

martin-a-brown
Copy link

Greetings Daniel,

I'm working with The Linux Documentation Project to improve automation and collection management. We now have automated publishing and hope to make some progress on some of the indexing and metadata managament questions.

Several months ago, you posted a request about your guide and whether it would be welcome in the TLDP collection. As part of my response to you (several weeks ago), I noted that I had made some minor DocBook 5.0 validation improvements.

This pull request includes all of these validation fixes that I found while examining your RTCQuickstartGuide document (as well as an ancillary symlink called RTCQuickstartGuide.xml pointing to book.xml).

Best regards,

-Martin

adjusting the attribute on <figure/> so that it says floatstyle="none" allows
the document to be validated (jing, against docbook.rng)
Adding a few <para/> elements so that the document will validate (<listitem/>
cannot contain bare CDATA)
the DocBook 4.x standard used format="linespecific" to number lines; the
DocBook 5.0 standard uses linenumbering="numbered" to mean the same thing
A <sect2/> cannot be a direct child of a chapter; however, a <section/> can.
This also obviates the need to keep track of whether something is a <sect1/>,
<sect2/> or <sect3/>.  And, <section/>s can be nested.
I do not know what is intended, and it is not in the DocBook 4.x nor DocBook
5.x references; commenting it out allows validation.
adding a symlink to the book.xml named RTCQuickstartGuide.xml;
TLDP convention is to have the document stem name be the same as an enclosing
directory (if there are multiple files)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant