USE_SAXON is set. This doesn't quite work yet.
Also fix a bug in the .fo target that was uncovered when slides for a
presentation are split across multiple XML files.
Norman Walsh's DocBook Slides DTD.
This DTD offers the vocabulary of simplified DocBook for
presentations. Initially, the supported output formats are PDF and
HTML.
XSL stylesheets are used so libxslt is required.
PassiveTeX is used for the PDF generation to convert the XSL-FO
directly to PDF.
This commit moves various TeX definitions out of doc.docbook.mk and
into doc.project.mk, since docbook is no longer the only back-end to
utilize TeX.
An example Makefile would look like :
----
DOCFORMAT= slides
DOC= slides
SRCS= slides.xml
DOC_PREFIX?= ${.CURDIR}/../../..
.include "${DOC_PREFIX}/share/mk/doc.project.mk"
---
And an example slides file (slides.xml) looks like :
---
<!DOCTYPE slides PUBLIC "-//Norman Walsh//DTD Slides XML V3.3.1//EN"
"http://docbook.sourceforge.net/releases/slides/3.3.1/slides.dtd">
<slides>
<slidesinfo>
<title>What's new in FreeBSD 5.3</title>
<titleabbrev>FreeBSD 5.3</titleabbrev>
</slidesinfo>
<foil><title>Introduction Slide</title>
<para>Content</para>
</foil>
</slides>
---
You could then build the HTML and PDF versions of the slides by typing
"make FORMATS='pdf html'". Enjoy.
Please coordinate with doceng@ before importing any presentations to
doc/.
Jade is not able to embed images but links them instead, so images have
to be installed with the .rtf document (it's similar to the HTML case).
I added a new format: rtf.tar which is a better solution than using rtf
since the images are not embedded.
make FORMATS=rtf.tar is your friend :)
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.
just after doc.common.mk included. This can be used for various
language specific customizations.
- Remove SP_ENCODING_LIST. Translators should define the SP_ENCODING
variable directly in their doc.local.mk when it is needed.
Discussed with: den
Currently we have articles.ent and books.ent, and
for example, articles.ent can be used by putting the
following lines in the doctype declaration:
<!ENTITY % articles.ent PUBLIC
"-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN">
%articles.ent;
This pulls all of the necessary entities via share/sgml/articles.ent.
The translation teams can customize these entities by redefining
the articles.ent file in <langcode>/share/sgml. See
ja_JP.eucJP/share/sgml for example.
