Thomas Schraitle | 30 Jun 08:53 2015

Time for new DocBook Stylesheet Release?


in the last years I've observed a trend, that the DocBook stylesheets
don't publish new releases very often.

The last release of the stylesheets is from 2013 which is two years old!
Am I'm the only one who need and wait desperately for a new release? ;))

I know, you are all busy with other things. However, I fear, this makes
the wrong impression that this project is dead. I hope this is not.

After two years I would love to see a new release. Maybe with a release
cycle which counts in months and not years?

Any plans? Thoughts? :)


    Thomas Schraitle
DeanNelson | 30 Jun 01:19 2015

Docbook XSL and FOP 2.0

I have tried to update our production documentation system to FOP 2.0 but in doing so I discovered a little problem that prevented the use of FOP 2.0. I get an exception and cannot get around it without recompiling with a fix. (See )
I am interested in other people's experience in using FOP 2.0. In your experience, is it really ready for prime time? Are you using it successfully?
I'm using the 1.78.1 stylesheets with Docbook 4.5.
Dean Nelson
Olivier Ishacian | 29 Jun 22:07 2015

New resources for those interested in DocBook 5.1 new assembly and topic elements

Two new resources for those interested in DocBook 5.1 new assembly 
andtopic elements:

* Free, open source, assembly processor: XMLmind Assembly Processor.

* Tutorial: DocBook Assemblies and Topics for the Impatient.
Olivier Ishacian | 29 Jun 22:00 2015

[ANN] Release of XMLmind XML Editor v6.3.1

XMLmind is happy to announce the version 6.3.1 of XMLmind XML Editor.

XMLmind XML Editor Evaluation Edition v6.3.1 can be downloaded from

Professional Edition users, please upgrade using this form:

(The above form is usually accessed through

XMLmind XML Editor v6.3.1 (June 24, 2015)


* Preliminary support for DocBook 5.1, which introduces new topic
   and assembly elements.

   This support is packaged as a new add-on called "DocBook v5.1
   configuration (Release Candidate)". This add-on is NOT included
   by default in XXE distributions. If you want to experiment with
   DocBook 5.1 assemblies and topics, please use menu item
   "Options|Install Add-ons" and select the add-on in order
   to download and install it.

   New resources related to DocBook 5.1:

    - New tutorial: DocBook Assemblies and Topics for the Impatient.

    - New documentation: XMLmind XML Editor - Support of
      DocBook 5.1 Assemblies.

    - New open source software: XMLmind Assembly Processor.

* Upgraded Apache Batik (SVG support) to version 1.8.
   Upgraded Apache FOP (PDF generator) to version 2.0.

* Several other enhancements (e.g. menu item "DocBook|Convert
   to Module") and a few bug fixes.

More information in


* DocBook Assemblies and Topics for the Impatient

* XMLmind XML Editor - Support of DocBook 5.1 Assemblies

* XMLmind Assembly Processor
Emery, Norma (HGR | 26 Jun 21:45 2015

Docbook to IETM?

Docbook experts,


I’m looking for information on how we could render our Docbook content as IETM deliverables. Does anyone know of relevant tools (e.g., transform scenarios?) to meet specific IETM functional requirements?




Norma Emery  

Peter Fleck | 26 Jun 20:24 2015

xi:include publisher


I moved our common xml files to a webserver and now publisher does not 
get included.

I'm using the following syntax:

<xi:include xmlns:xi="" 

It works great for <legalnotice>, for <colophon> etc and it worked when 
the file was local (though that doesn't mean it was correct).
Is it because <publisher> is not a block item? Is there a better way of 
including the common <publisher> across documents?


Thomas Schraitle | 22 Jun 12:43 2015

[ANN] DAPS 2.0 released


after more than two years of development, 15 pre-releases and more than
2000 commits we proudly present release 2.0 of the DocBook Authoring
and Publishing Suite, in short DAPS 2.0.

DAPS lets you publish your DocBook 4 or Docbook 5 XML sources in
various output formats such as HTML, PDF, EPUB, man pages or ASCII with
a single command. It is perfectly suited for large documentation
projects by providing profiling support and packaging tools.

DAPS supports authors by providing linkchecker, validator,
spellchecker, and editor macros. DAPS exclusively runs on Linux.

Download & Installation

For download and installation instructions refer to 
Highlights of the DAPS 2.0 release include:

* fully supports DocBook 5 (production ready)
* daps_autobuild for automatically building and releasing books from
  different sources
* support for EPUB 3 and Amazon .mobi format
* default HTML output is XHTML, also supports HTML5
* now supports XSLT processor Saxon6 (in addition to xsltproc)
* improved "scriptability"
* properly handles CSS, JavaScript and images for HTML and EPUB
  builds (via a "static/" directory in the respective stylesheet folder)
* added support for JPG images supports all DocBook profiling
* attributes
* improved performance by only loading makefiles that are needed for
  the given subcommand
* added a comprehensive test suite to ensure better code quality when
* tested on Debian Wheezy, Fedora 20/21 openSUSE 13.x, SLE 12, and
  Ubuntu 14.10.

  Please note that this DAPS release does not support Webhelp. It is
  planned to re-add Webhelp support with DAPS 2.1.

For a complete Changelog refer to


If you have got questions regarding DAPS, please use the discussion
forum at  We will
do our best to help.

Bug Reports

To report bugs or file enhancement issues, use the issue tracker at

The DAPS Project

DAPS is developed by the SUSE Linux documentation team and used to
generate the product documentation for all SUSE Linux products.
However, it is not exclusively tailored for SUSE documentation, but
supports every documentation written in DocBook.

DAPS has been tested on Debian Wheezy, Fedora 20/21 openSUSE 13.x,
SLE 12, and Ubuntu 14.10.

The DAPS project moved from SourceForge to GitHub and is now available

Have fun! :)


    Thomas Schraitle
Janice Manwiller | 19 Jun 16:47 2015

Problem with xi:include of section

I'm trying to include a section from one document into another document.

In the source file, the xi:include is:

<xi:include href="ref_config_object_json.xml" xpointer="config-obj-dashboard" xmlns:xi="" />

This resolves correctly in the XML editor.

When I try to build the document (we use the Docbkx Maven plugin), the build fails, with the following error:

org.xml.sax.SAXParseException; systemId: file:///Users/janicem/Documents/sqrrl/doc/src/xml/dat_sqrrl_ui_dashboard_configure.xml; lineNumber: 192; columnNumber: 128; Include operation failed, reverting to fallback. Resource error reading file as XML (href='ref_config_object_json.xml'). Reason: XPointer resolution unsuccessful.

Error on line 192 column 128 of file:///Users/janicem/Documents/sqrrl/doc/src/xml/dat_sqrrl_ui_dashboard_configure.xml:

Error reported by XML parser: An 'include' failed, and no 'fallback' element was found.

Error on line 62 column 90 of file:///Users/janicem/Documents/sqrrl/doc/src/docbkx/SqrrlDataMgmtAnalysis.xml:

  Error reported by XML parser: Error attempting to parse XML file (href='../xml/dat_sqrrl_ui_dashboard_configure.xml').

Error on line 174 column 68 of file:///Users/janicem/Documents/sqrrl/doc/src/docbkx/SqrrlGuides.xml:

  Error reported by XML parser: Error attempting to parse XML file (href='SqrrlDataMgmtAnalysis.xml').

After looking at the DocBook docs, I tried adding a DOCTYPE entry with the DTD, but that didn't work either.

So is this xpointer syntax just not supported in this case? Or am I just missing some other setting?



Andy Hatton | 16 Jun 17:35 2015

Webhelp stemming and search indexer


I am using the DocBook XSL stylesheets (version 1.78.1) to produce Webhelp, and my documents are being translated into French, Japanese, Korean, and Simplified Chinese.

I have a couple of questions about configuring the Webhelp search which do not seem 100% obvious to me, having looked through the Webelp docs.

(1) The Webhelp XSL templates always output a link to a JavaScript stemmer library. The file name of the library linked to is determined by the webhelp.indexer.language parameter. But Webhelp only includes stemmers for en, fr and de languages.

Question 1: Is it OK to use the default "en" JavaScript stemmer with non-English locales, or is it best to customize the template that outputs the stemmer link and remove the link for languages that do not have a stemmer?

(2) The Java indexer command used with the Webelp build has the properties webhelp.indexer.language and enable.stemming.

In trying to establish a list of languages that have Java stemmer support, the Webhelp docs have this:

- In the section "Adding support for other (non-CJKV) languages") there is a list of non-CJKV languages that have stemmer support but no language codes.

- In the section "Search indexing" it says look in the file for the language code, but the file says look in the docs.

- In the section "New Stemmers" (in the developer docs) it seems to indicate a different list of languages with stemmers, with a list of language codes (including "cn" for Chinese?).

Question 2: If the enable.stemming property if set to true, is the value of webhelp.indexer.language used to determine whether a Java stemmer is used?

Question 3: Is there a definitive list of language codes that the Java indexer expects/accepts/supports for the language?

Question 4: If a language has no Java stemmer, is it best to set the enable.stemming property to "false", or does it not really matter?


Peter Desjardins | 2 Jun 21:33 2015

Index entry fo:block disrupts keep-with-next.within-column

I noticed a section title separated from the first paragraph in its
section by a PDF page break. The title of the section is at the bottom
of one page and the first paragraph at the top of the next page. I'm
using the docbook-xsl-ns-1.78.1 stylesheets.

The problem is caused by an index entry between the title and the
first paragraph. If I remove the index entry, the title is kept-with
the following para.

The index entry results in a fo:block to mark the internal destination:

  <fo:block id="d0e240"><!--containers--></fo:block>

So the title is satisfied with being kept-with the index entry fo:block.

I am considering customizing the fo:block for index entries to add a
keep-with-next.within-column="always" attribute.

Does anyone know of a better way to prevent index entries from
interfering with keep-with-next behavior?



****** My DocBook *****

<section xml:id="containers-about">


   <para>Containers ...

****** The corresponding FO *****

      <fo:block keep-together.within-column="always" margin-left="0pt"
        <fo:block keep-with-next.within-column="always">
          <fo:block font-family="sans-serif,Symbol,ZapfDingbats"
font-weight="bold" keep-with-next.within-column="always"
space-before.minimum="0.8em" space-before.optimum="1.0em"
space-before.maximum="1.2em" text-align="start" start-indent="0pt">
            <fo:block font-size="12pt" color="#405D99"
font-weight="600" space-before.optimum="2.0em"
  <fo:block id="d0e240"><!--containers--></fo:block>
  <fo:block space-before.optimum="1.7em" space-before.minimum="1.5em"
    Containers ...
Paul DuBois | 27 May 18:55 2015

Changing <formalpara> title formatting

For <formalpara>, the <title> normally is formatted with a period added to the title. For example, this:


   <title>Formal Para Title</title>

     Formal para content.

Appears like this, with the title in bold:

Formal Para Title.  Formal para content.

I have a document that's being translated into Japanese. My translators tell me that for Japanese, it's
better not to have the period added to the formalpara title.

I thought perhaps changing the document from lang="en" to lang="ja" might do the trick, but no dice. Is
there a supported way to do this? I don't want to hack my stylesheets in an untoward way because I don't want
to affect other documents. Thanks.