Effective from dosemu-1.0.1 the documentation format for DOSEMU is DocBook. Currently this is DocBook 3.0, but formatted in lower case for XML compatibility. This will probably be migrated to DocBook 4, but the changes are unlikely to affect most authors.
Every programmer can handle the few basic DocBook commands that are need to make some really good documents! There are many similarities with HTML, which is hardly surprising as they are both SGML narkup languages. The source to this document may make useful reading (This is the file ./src/doc/README/doc)
There are 5 section levels you can use. They are all automatically numbered. Your choices are:
A top level section. This is indexed.
A 2nd level section. This is indexed.
A 3rd level section. This is indexed.
A 4th level section. This is not indexed.
A 5th level section. This is not indexed.
You cannot skip section levels on the way up or down (ie you must go <sect>,<sect1>,<sect2> and not <sect>,<sect2>). You must also close each section when you finish it. This includes the enclosing sections.
The title of the section must be enclosed within <title>...</title> tags.
Each paragraph of text must be enclosed within <para>...</para>.
There is only one way to do this.
Emphasises text like this.
Here we have 3 useful types:
A standard bulletted list
A "numbered" list
A description list (like this)
For ``itemizedList'' and ``orderedList'' the items are marked with <listitem>. eg:
<itemizedList> <listitem><para> item 1 </para></listitem> <listitem><para> item 2 </para></listitem> </itemize>
For the ``variableList'' the items have two additional markers. Each entry in the list is enclosed in <varlistentry>...</varlistentry>. Each ``term'' is marked using <term>...</term> and then the content is marked with listitem, as above. eg:
<variableList> <varlistentry><term>item 1</term><listitem><para> is here</para></listitem></varlistentry> <varlistentry><term>item 2</term><listitem><para> is here!</para></listitem></varlistentry> </variableList>
If you want to quote a small amount use <literal>...</literal>. eg:
This is <literal>./src/doc/README/doc</literal>
To quote a large section, such as part of a file or an example use <screen>. eg:
<screen> ... </screen>
You still need to ``quote'' any <, > or & characters although most other characters should be OK.
Obviously some characters are going to need to be quoted. In general these are the same ones as HTML. The most common ones are:
One of the extra feature that this lets us do is include URLs and cross-references.
These have 2 parts: a label, and a reference.
The label is <... id="...">. ie an id on the element you want to refer to.
The reference is <xref linkend="..." >. The linkend should refer to an id somewhere else in the same document (not necessarily the same file as the README's consist of multiple files). The section naem will be inserted automatically at site of the <xref>.
This is <ulink url="...">...</ulink>. The url will be active only for HTML. The text will be used at all times. eg:
See the <ulink url="http://www.dosemu.org/">DOSEMU website</ulink>.
Whilst it is possible to do insert email addresses as URLs there is a better way. Simply enclose the address in <email>...</email>. eg:
Here are a few other places to find information about writing using DocBook.
``DocBook: The Definitive Guide'' is a complete reference to DocBook. It is an O'Reilly book, which is also readable online.
This is a basic guide to DocBook.
Part of the Linux Documentation Project (LDP) this is a guide to writing HOWTO's specifically, but covers DocBook in general as this is now the preferred MarkUp for the LDP.