well as the lack of necessity of duplicates) in revision 1.142 (adding
PAM manual pages).
Found by: ../examples/check-manref.sh
Submitted by: sed, xargs, ../examples/add-manref.sh
Someone on the RE team will reinstate this change when the release is
imminent.
This (hopefully) will prevent people reading our doc files from getting
confused as to what the latest release is.
Approved by: murray
repo-copy from sound). This is based on the old sound chapter, but
includes video and other multimedia related bits. More will be added to
it shortly and various parts will be cleaned up, but I wanted to get
this in the tree before I do anything else to it.
The sound chapter has been removed from the build, but I haven't cvs
rm'd it yet (though I will in about 24 hrs time).
Mostly submitted by: Ross Lippert <ripper@eskimo.com>
Add support for using the XSL stylesheets to generate HTML output using
XSLT transforms, rather than using JadeTeX. So (assuming you have
installed xsltproc from ports/textproc/libxslt, and the docbook-xsl
stylesheets), you can now do
make STYLESHEET_TYPE=xsl FORMATS=html
and get HTML output that way.
'xsl' a different set of rules are invoked to use an XSL toolchain
(processors, stylesheets, and so forth) to convert the DocBook to the
various different output formats.
I haven't actually written the rules that are invoked when this knob is
set to 'xsl'. But how hard can it be. . .
If defined, EPS files are run length encoded before being integrated
into the PostScript output.
"make book.ps" currently generates a 96 megabyte file.
"make RLE=1 book.ps" generates a 16 megabyte file.
If we added a tool to use better (LZW) compression for the eps
screenshots and such, then we could reduce this number further.
Don't make the assumption that source files are writable.
The FDP infrastructure has a few constructs of the form
"cp foo bar; cat baz >> bar". This breaks if foo isn't
writable (as is frequently the case in P4 work directory).
<filename role="package">. The <port> tag as it was had two major
defects: (a) the name is ambiguous (does "port" mean "architecture"?
how about "TCP/UDP port"?), and (b) it introduces a non-standard (to
DocBook) tag, which is generally assumed to be evil.
Moral support by: bmah, keramida, mwlucas, roam
stylesheets. To get around this, append the filename specified in the
'CSS_SHEET_ADDITIONS' variable (if defined) to the end of the default
CSS stylesheet. This allows us to add document-specific stylesheet
rules while still supporting braindead browsers and reusing the
default CSS code.
