Bob Stayton | 9 Feb 01:33 2016

NVDL, DocBook, and MathML

I'm having a problem trying to process DocBook 5 documents using NVDL in 
order to validate DocBook content that has MathML content within 
equation or inlineequation.  The DocBook validation side is failing, but 
only under NVDL.

The DocBook rng schema for inlineequation is as follows:

    <define name="db.inlineequation.content">
                <ref name="db.inlinemediaobject"/>
                <ref name="db.mathphrase"/>
             <ref name="db._any.mml"/>

This schema specifies either a) inlinemediaobject or mathphrase, or b) 
some MathML elements.  It *allows* MathML, but it does not validate it 
against the MathML DTD.  NVDL is capable of doing that.  But ...

When I set up NVDL using a schema like this:

<rules xmlns="" 
(Continue reading)

Kallauch, Benjamin (EEIN/5 | 4 Feb 15:57 2016

Centered table cells

Dear community
I encountered a problem using XSL --> FO where I can’t get centered table cells (horizontally). In my opinion the cause is in a false fo-structure, where the ‘text-align’ attribute is set in the fo:table-cell element rather than in the fo:block child element.
The problem is maybe well known and solved long ago. Please, forgive me, but I feel overwhelmed by the huge amount of hits when searching the group. Can anyone please direct me to a solution, if there is any?
Thanks and best regards,
Frank Arensmeier | 4 Feb 12:12 2016

Content model for caption wrong?


I am reading the content model definition for the "caption" element -
The content model clearly states that captions can contain plain text. However, this little snippet does not pass validation in Oxygen:

<section xmlns="" xmlns:xlink="" version="5.0">
<title>Section Template Title</title>
<imagedata fileref="#"></imagedata>
        <caption>My caption here.</caption>

Is the content model wrong or the Docbook RNG Schema?

Frank Arensmeier

Paligo - The truly user-friendly CMS for technical documentation

Frank Arensmeier | 3 Feb 20:59 2016

Caption on informalfigure not recognised by PDF stylesheet?

Hi there!

I came across an issue with the PDF stylesheets, but I am not sure if it is a bug nor not. Assume I have the following XML:

<section xmlns="" version="5.0">
<title>Section title</title>
<para>Some para</para>
<para>Caption comes here</para>

The snippet validates as valid Docbook XML but the resulting PDF however shows the caption element in red (no matching template found). I am using 1.78.1. Can someone confirm that this is a bug?

Thank you!

/Frank Arensmeier

Paligo - The truly user-friendly CMS for technical documentation

Nico van de Water | 20 Jan 10:06 2016


Dear list members,


Is there anyone here with (a lot of) experience with <glossentry> and related tags? A friend of mine is running into problems with DITA-based glossary entries.


With thanks and best regards,


Warren Block | 19 Jan 05:42 2016

Preserving entities and language translation

Some of the articles in the FreeBSD documentation use entities to 
include large blocks of data.  For example, one article is just a very 
large list of PGP keys for developers:

The DocBook article.xml is only 2K, because it does things like this:

   <sect1 xml:id="pgpkeys-officers">


We use xmllint to normalize the article into a single XML file for use 
with PO translation tools.  Of course, all entities are expanded into 
text at that point.

It would be really nice to mark that particular entity as one that 
should be preserved in the translated file.  Is it possible to do that 
with processing instructions or some other method?  For example:

   <sect1 xml:id="pgpkeys-officers">

     <?translate off?>
     <?translate on?>

In the normalized file, it could be a string to indicate to translators 
that it should be left alone:

   <sect1 xml:id="pgpkeys-officers">

     <?translate off?>
     do not translate: section.pgpkeys-officers
     <?translate on?>

Of course, it has to be changed back when the translated XML file is 

Is there a standard or elegant way to do this?
Alexander Garcia Castro | 15 Jan 07:30 2016

Fw: new important message



New message, please read


Alexander Garcia Castro

Erik Leunissen | 11 Jan 00:55 2016

Recommended docbook element for a "Problems section"

Hi all,

I'm in the process of writing an educational textbook. The textbook is a 
docbook book, containing several chapters. Each chapter contains several 
sections with "explained content", a "Problems section" and a 
bibliography. Like the sections, the "Problems section" and the 
bibliography occur at the same level just below a chapter.

(B.t.w. the word "section" in "Problems section" is just a matter of 
speak, not meant to be a docbook element, not yet anyway)

Sample document structure:

Table of contents
Chapter 1
   1.1 First section
   1.2 Second section
   1.3 Third section

Chapter 2


My question relates to the "Problems" section in each chapter. Like the 
bibliography it must not have a label, but must occur in the table of 

I've been looking for a docbook element for such a "Problems section", 
and I have difficulty finding an appropriate one:
- I can't make it a docbook section because these are processed to 
display a label.
- a Q&A set seems inappropriate since there are only questions (which 
are not "Frequently asked" anyway; and answers are not supposed to be 
provided in the same structural element)
- I've been thinking about using a section element with a dedicated role 
attribute, that triggers customized processing, but that's just a wild 
idea for now.

In case it matters: my processing toolchain is:
   docbook5 XML | xsltproc | fop | pdf

I'd appreciate very much any suggestions,

Erik Leunissen.
Pc Thoms | 9 Jan 14:02 2016

Indexterms with emphasis and citetitle elements

When generating an index using 1.79.0 the <emphasis/> and <citetitle/> elements do not produce any italicized text in an index generated in pdf, or xhtml.
Would like this to work.

Pc Thoms | 8 Jan 15:52 2016

Indexterms with one or more See elements

While working on a legacy project I found the following to be valid:

<indexterm><primary>Engineers</primary><see>North of England</see></indexterm>

This produces an entry that appears as

Engineers (see Institution) (see North of England)

and usually the see would italicized in an index. 

However, the following is does not validate.

<indexterm><primary>Engineers</primary><see>Institution</see><see>North of England</see></indexterm>

On the page,, there is reference to "if there is at least one see entry for a particular term." This to my mind implies that there may one or more see references.

When consulting the Chicago Manual, Edition 17, the first example is an entry with see two different entries, as follows:

adolescence. See teenagers; youth

Edition 16, however, has only single see entries in its' examples.
Winslow Dalpe | 8 Jan 08:08 2016

Small questions RE: the xslt2 stylesheets

I've forked and been making some changes to the xslt2 stylesheets for a 
personal project, and I'm trying to get some of those changes into a 
shape where they might be pull-requestable. A few of them are very 
small, but I have some questions about the intended functionality.

1. The `olink.doctitle` parameter is a numeric type by default in the 
stylesheet params definition, but the stylesheets compare it as a string 
in one place

and a numeric in another

Which is supposed to be correct? Numeric makes more sense to me personally.

2. The Docbook schema says that only one `glossterm` may exist as a 
direct child of a `glossentry`. But the stylesheets have contingency for 
multiple `glossterm`

(which is actually a very useful feature even though it's "wrong"). 
Unfortunately, other code

will crash if multiple `glossterm` exist (node-set will get passed into 
normalize-space which will fail). Is it preferable to remove the 
contingency templates, or to "correct" the crashing code to handle the 
"bad" case?

Thank you,
Winslow Dalpe