the charset of HTML files generated from an DocBook/SGML file.
Note to translators:
While some of the translations already use this tweak
in their localized freebsd.dsl, it is no longer needed so
removed and the necessary changes have been added instead.
After this commit, please make sure to define
&doc.html.charset; in <langcode>/share/sgml/l10n.ent.
If not defined, iso-8859-1 is used by default and it can
break the translation.
Discussed on: -doc
specify the image extension (png) and force callouts text markers.
The callout markers from 1 to 9 are not correctly rendered under
OpenOffice (I don't know about other rtf viewers). I don't have a
solution for this problem for the moment.
attribute in acronym DocBook tags and use this for the title attribute
in acronym HTML4 tags, which will then give a mouseover definition of
the acronym.
format it properly with the \TeX command. Likewise for instances of
LaTeX in our documentation.
There should be no change for the HTML output, where they will still
be rendered in bold characters like all other text wrapped in <application>.
of %show-all-trademark-symbols% from the HTML only section to the
general section.
Reported by: Jon Allen <jonallen@paunix.org>, bmah
Pointy hat to: simon
required symbols, by setting the make variable
WITH_ALL_TRADEMARK_SYMBOLS, to any non empty value.
This feature is mainly useful for document writers, to make sure all
trademarks are marked up correctly.
Each trademark will only have a trademark symbol appended the first
time in a document for print / html, and the first time on each HTML
page for html-split.
It is possible to always append the trademark symbol for a trademark,
by setting the role attribute to "force" in the trademark tag.
The code differentiates between trademarks in normal text and titles,
so if there is a trademark in a title, the symbol will be displayed
the first time in the title, and the first time in the normal text.
Basically this means that all trademarks can / should be marked up in
the documents, and the stylesheet will do "the right thing".
Looked at by: murray
Approved by: mwlucas (temp mentor)
and the localized sysids to <langcode>/share/sgml/catalog.
Since <langcode>/share/sgml/freebsd.dsl still include some
language-neutral parameters and procedures for printable formats,
I will work on assorting them similarly. I am sorry that
this (and probably the next) commit may break the translation
team's usual update procedure, but you can merge the language-specific
freebsd.dsl from the English version as before.
Discussed on: -doc
enable it in en_US.ISO8859-1/ and ja_JP.eucJP/.
- Add PUBLIC "-//FreeBSD//ENTITIES DocBook Language Specific Entities//EN"
and l10n.ent for entity localization.
- Use share/misc/docbook.css for indentiation of <programlisting>
and <screen>.
- Add some missing $FreeBSD$.
- WITH_INLINE_LEGALNOTICE (for HTML only):
do not render <legalnotice> as a separate file if defined.
- WITH_ARTICLE_TOC:
generate TOC for documents whose root element is <article> if defined.
- WITH_BIBLIOXREF_TITLE:
for cross references to bibliography entries, use the title of
the entry as the cross reference text, if defined.
'text-only' case.
Do this by explicitly setting preferred-mediaobject-notations to the
empty list.
This has only worked for so long because the source format for images in
all the documents with plain text equivalents for images has been EPS,
which isn't used in the HTML output format. If PNG images were used
then the <textobject> element wasn't chosen.
<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
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.
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
specific construction rule instead of duplicating code when we want to
conditionally alter the stylsheets.
Suggested by: Norman Walsh
Referenced in: ISO/IEC 10179:1996(E) p180-181
