Default to "IGNORE", you should set them to "INCLUDE" by whatever
mechanism your SGML parser supports as necessary (i.e., Jade's -i
flag).
Added redefinitions for some ISO entities that aren't understood by
most web browsers. Since this is for HTML output only, wrap it in a
%output.html; marked section.
Use these marked sections to put both print and HTML stylesheets in one
.dsl file (freebsd.dsl). The print stylesheet now understands about the
elements that have been added to DocBook (and won't try and render them
in red).
Updated Makefile to use output.html and output.print on the command
line to Jade, instead of the earlier "html" and "print.
Note: producing .tex (and thence .ps and .pdf) versions of the Handbook
is broken. The Handbook tickles several bugs in the JadeTeX macros.
Sebastian Rahz, the JadeTeX author, knows about this, and is working on
fixing them.
- Turn off the shading of verbatim environments. Replace with our
own scheme which wraps these in <blockquote>, more in keeping
with other documents.
- Specify the root filename for the HTML version as 'index.html'
DocBook stylesheet (ports/textproc/dsssl-docbook-modular) and extends it
in three ways.
First, Norm's stylesheets have a number of documented 'knobs' that can be
twiddled to produce specific effects. For example, one of the options I've
turned on names the generated HTML files after the id attribute of a
section. Say goodbye to c01234.html, and wave hello to 'kerneloptions.html'.
Second, some of Norm's design choices don't follow our existing practice.
For example, we indicate application names in bold, command names in a
monospace font. Norm's sheets just render command names in bold. So we
override his definition with our own for some elements.
Thirdly, we tell the stylesheet about elements that don't exist in DocBook
but do exist in our extended DTD.
Tim Vanderhoek is probably sliding off his seat about now :-)
There's more that needs doing to this, but it's enough to get start with.
Extends DocBook v3.0, with (currently) the following additions.
1. <hostid>, <username>, <devicename>, <makevar>, and <maketarget> have
been added. Sample uses would be be.
<para>By convention, the the local machine can always be referred
to as <hostid>localhost</hostid>, with the IP address
<hostid role="ipaddr">127.0.0.1</hostid>.</para>
<para>The most powerful account on the system is
<username>root</username>, able to leap tall buildings in a single
bound.</para>
<para>Some devices have an entry in <filename>/dev</filename>. For
example, <filename>/dev/cuaa0</filename> corresponds to
<devicename>sio0</devicename>. Other devices, such as
<devicename>ed0</devicename> do not have entries in
<filename>/dev</filename>.
<para>To rebuild the system, use the <maketarget>world</maketarget>
target. If you do not want to build profiled libraries then ensure
that <makevar>NOPROFILE</makevar> is set.</para>
2. <FAQList> has been added as a new list type, with its own listitem.
Use like so;
<FAQList>
<FAQListItem>
<FAQQuestion>
<para>I have bad blocks on my hard drive!</para>
<!-- Nothing restricting a question to one paragraph -->
</FAQQuestion>
<FAQAnswer>
<para>With SCSI drives, the drive should be capable…</para>
<para>…</para>
</FAQAnswer>
</FAQListItem>
</FAQList>
Long winded, but comprehensive, and in keeping with the rest of DocBook.
As I convert the handbook from LinuxDoc to DocBook I'm working on an
extensive markup guide for the project, where constructs like these will be
fully documented.
