[ fromfile: styletest.xml id: styletest ]

	What is Slacker's Docbook?
	hi there

Slacker's Docbook is two things.

Most of the non-Docbook tags added to Slacker's Docbook will be familiar to anyone who has edited an HTML page, since they were taken from HTML.

It is much faster and easier to compose Slacker's than to use standard Docbook/XML.

The scripts are organized and deployed by Apache Ant, an open source, cross platform, Java-based build tool.

Output format is controlled by easily customizable stylesheets which we have provided.

The use of several Slacker's Docbook tags and directives is demonstrated below.

This text is in a condition=“textbook” element, so it only appears in the textbook version.

ant bookhtml or ant pdf both generate versions that include textbook elements. An alternate way of describing textbook conditionals is with the <textbook> tag. This is equivalent to a <p condition=“textbook”>

Figure 2.  A title for a figure

An admonition is a Docbook tag with a title and an associated icon.

Here are the available admonitions. The original Docbook admonitions are all supported in Slacker's Docbook; however, we have added two new tags: <prereq> and <question>.

	Warning
	Danger Will Robinson. Things to be careful about.

	Caution
	Cautions can be dangerous to your health. They happen to be mapped to <warning> anyway.

	This is a note
	Take note of that. It's important!

	Important
	This is actually not so important, since it's mapped to <note>.

	Tip
	This is a tip. It's very good advice. It could save you time.

	Question
	The Docbook meaning of <question> remains the same if it appears inside a <qandaset>. However, if it appears where a other admonitions are allowed, <question> is mapped to the docbook important admonition.

	Prerequisites
	This is inside a <prereq>. It's mapped to the <caution> admonition since we are not using it.

The glyphs are taken from Bobco fonts, with copyrights held by the Subgenius Foundation ^[2].

A formalpara about parabullet (<pb>) .  This is a <formalpara> which is discussing the parabullet that follows. parabullets are very interesting because they are rendered quite differently depending on which version you are generating. In order to simultaneously write bullet-text for the slides version and paragraph text in the book version without repeating yourself, mark each paragraph as a <pb>, marking up each major idea in it as an <li>.

This content is inside <pb>, which is short for parabullet. When a <pb> is encountered, and condition['slides'] is not true, we translate <pb> into <para>, stripping all <li>s. Otherwise, the preprocessor translates each <li> into a <listitem> <para> and the <pb> maps to an <unorderedlist>. They appear as bullets in the slides version and paragraphs in the textbook. This means that unordered lists inside <pb>should be properly punctuated. <li> is much easier to type than <listitem> <para>.

Todo items.  The <todo> element is mapped to <p> but also has a bold heading that says “Todo Items”.

This is a paragraph marked conditionally with remark, but using the abbreviated c= attribuite. Since it is a remark, it should only be visible in the development version, and is styled for remark.

The remark tag is just shorthand for a para class=“remark”

ant dev Generates the HTML “development” version which contains every conditional included in the output, highlighted in different colors as specified in the css file.

We can include xml files as mode=“text” (the default for all files which do not have a .cpp or .h suffix). It does simple line-wrap.

<section id="example"
    xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance"
    xsi:noNamespaceSchemaLocation =
'http://slackerdoc.tigris.org/xsd/slackerdoc.xsd'>
  <title> Slackers Docbook - example </title>

  <p> Including sourcecode is straightforward with the <tt>
&lt;include src=&quot;filename.xml&quot; /&gt; </tt> element. </p>

  <include src="impl.xml" />

  <p> Including images looks very similar to HTML except we typically
enclose them in a <tag>figure</tag>, like so: </p>

  <figure id="somefig"> <title> This is the title of the figure
</title>
    <img src="./uml/xml2html.png" />
  </figure>

  <section id="dtdtoc">
  <title> DTD catalog </title>
  <p> Xml2docbook generates a DTD to define entities for each included
file, as well as each generated XML file: </p>

  <include src="html/00-generatedEntities.dtd" />

  <p> This makes it a lot easier to include sub-documents. If they are
located in subdirectories, their entity names are based paths derived
from relative (to your xml document) pathnames.
  </p>
  </section>

  </section>

Todo items.  Add conditional inclusion tags for XML inside proper XML comments.

When including C++, you can use //start and //end comments to switch on/off inclusion.

In addition, c-style comments appear as callouts in the listings.

Click on filename, or the “link” icon below the included code to see the original file before processing. Notice we only see a small piece.

[ . . . . ]
    
    /* Insert a menu into the menubar. */
    QMenu *menu = new QMenu("&Questions", this);

    QMainWindow::menuBar()->addMenu(menu);
    
    /* Add some choices to the menu. */
    menu->addAction("&Ask question",
                    this, SLOT(askQuestion()), tr("Alt+A"));
    menu->addAction("Ask a &dumb question",
                    this, SLOT(askDumbQuestion()), tr("Alt+D"));
}

In this next example, there is no link, and in fact, the included file has restricted permissions, so you should not be able to see it even if you guessed at its url.

[ . . . . ]

int main() {
    Point p(1,1);
    const Point q(2,2);
    p.set(4,4);  
    p.print();
    q.set(4,4);  
    return 0;
}