to fix a bug that would cause footnote numbering to be messed up if
using %footnote-ulinks% and we had any empty <ulink></ulink> elements
in a document. (This happens a lot in the release documentation.)
This change has been submitted to the DocBook bug database on
SourceForge as bug #502066. When it gets included into the
DocBook DSSSL distribution and the corrected version gets incorporated
into the FreeBSD Ports Collection, I'll back out the change in our
(FreeBSD's) stylesheet.
combination of %footnote-ulink% and bop-footnotes not generating any
URL footnotes (although other footnotes in documents were
correct). freebsd.dsl contains a modified definition of the
ulink element as defined in dblink.dsl from the DSSSL print stylesheet;
unfortunately it was missing some lines of code, which we restore.
As of this commit, no document in the FDP uses %footnote-ulink%,
although the release documentation will enable it shortly.
in the FAQ to use these. (Presumably there'll be others.)
While I'm here, add an entity for the current release's errata file.
Heavily based on the last patch in the PR, modified to be consistent
with the way that the Website build defines similar entities.
PR: 30202
Submitted by: Michael Lucas <mwlucas@blackhelicopters.org>
entities throughout the install chapter. These need to be defined
with so that these buttons don't wrap across lines.
This prevents :
"Press the [
OK ] button"
from showing up in the print or HTML output.
thinks that it must never output something like "_" to the TeX
backend, and should instead use \char{95}. The package we are using
to hyphenate URLs, url.sty, is designed to allow URLs without worrying
about such things, and will literally display the \char{95} without
this patch.
of the functions to get correct page numbering for two sided output.
This code will also have to insert some blank pages to make sure part
and chapter headers always start on a verso page. This is an
improvement, but it is also a work in progress that should be in the
tree so others can experiment with it.
The most visible impact is that the Chapter 1 now starts on page 2
instead of page 1. Part I now starts on page 1 instead of xviii.
When this is done properly, Chapter 1 will start on page 3.
prevents the majority of the remaining margin overflows. However,
this solution isn't very elegant in that it completely ignores
<replaceable>s inside of a <filename> element. The normal TeX that
gets output inside of \url{..} confuses TeX, so we must simply process
the children of replaceable without doing any additional formatting
inside of the \url{..} (such as putting the text into italics).
More work needs to be done on this.
to make the paragraphs right justified using TeX's default hyphenation
rules. We still must add some hooks to certain elements (URLs) to
deal with special cases that TeX can't hyphenate well.
by default for printed output. It turns out that this combination results
in URLs running of the right margin of the printed page.
This back-out is a temporary work-around to fix the PS/PDF
documentation for the impending 4.4-RELEASE.
Approved by: murray
This target finds all <programlisting role="pgpkey"> elements in the
Handbook and writes out a flat text file suitable for importing into
PGP or GPG.
This can be used in the web build to automatically update the public
keyring of FreeBSD developers.
