graeme | 29 Aug 17:26 2014

Support for the <result> inside <procedure> elements

Hi there,
I’m currently using Docbook 5.1b7 and have found that I really want to
be able to use the <result> tag, as described in the 5.1 guide here: 

The DocBook guide says that the <result> tag is supported but it doesn’t
seem to be supported by the docbookxi.rng schema. 

Putting a <result> tag inside a <procedure> generates this error when

    element "result" not allowed anywhere; expected the element end-tag
    or element "step"

Would anyone be able to advise me how to modify the schema to enable the
use of the <result> tag?

Thanks for your help,

Maciej Danielak | 28 Aug 16:07 2014

Generating TOC in nested sets

I have nested structure of set->sets->books->parts->articles. To generate ToC I'm using parameter generate.toc with value 'set toc, book toc, part toc'.

What I want is to create toc for a root set. Right now all "child" sets have generated ToC, while my root set remains empty. Is there a way to generate TOC in main set?
David Jackson | 20 Aug 02:40 2014

Simple title page - would like to add a logo

I have been using Docbook for just a week or so to create a user manual. 
I am using the DEP4E Eclipse plugin to author the Docbook text. DEP4E is using Docbook 5.
I only want to create the output in two formats - Eclipse Plugin Help and PDF.
This question relates just to the PDF output.  

All has gone well and I would like to now add a logo to the left of the title but so far have been unsuccessful at accomplishing what initially seemed like a  simple task. 

So my first question is this even doable - or must I get into the realms of XSL customization to accomplish this?  
I am not sure how flexible DEP4E might be in allowing a customization layer to be created.    

Ideally, I would like to format the book title to be approximately 1/3rd down form the top of the front page but I will worry about that later once I get a handle on if the logo can be inserted.
Sorry if this is a dumb question but picking this up has been a learning curve. 


Phillip Kent | 19 Aug 12:01 2014

Using topic and assembly - starting from article?

Dear all,

can someone give me a steer about this...

I currently have a collection of standalone documents, each is a
DocBook <article> .

I want to organise these into a more structured form, particularly so
that I can get them all to come out in a single PDF document (grouped
into super-topic chapters/sections...).

The topic and assembly elements in DocBook 5.1 look ideal for that
purpose. Is that correct?

If yes, how can I move from <article> to <topic>? I want one article
to become one topic, I don't need to chunk them into smaller parts.

Could I simply replace <article> by <topic> in each xml file and
nearly everything will work without further editing?

Thanks, Phillip
Carlos Araya | 16 Aug 23:59 2014

removing inline attributes from tables

I'm trying to cleanup my (x)html to use with epub3. One of the things I need to do is to remove inline attributes from tables as they ware not needed or controlled through CSS. 

How do I change the default behavior for tables? Is there a way to move this all to be CSS driven 


Peter Fleck | 14 Aug 11:11 2014

<cite> with class and title


I'm using a third-party javascript that requires the <cite> tag with the 
class and title populated.
I can't work out how to do it in docbook.

I have used the below as a temporary work around which works but would 
prefer it in docbook if possible.
<html:cite class="---" title="---">Cited Content</html:cite>


Ken Morse | 13 Aug 18:12 2014

Minimum TOC depth?

Has anyone figured out a way to have a minimum TOC depth? With HTML output, I'll sometimes see a page that has a single TOC that simply points to the first section -- in that case, it would be really nice to just skip the TOC.

(On a related note, with chunk.first.sections turned off, even when there are multiple items in the TOC, the first item will often be a link to something that's already visible on the page, which is sometimes not all that useful).

graeme | 13 Aug 15:04 2014

Release of DocBook 5.1 + XSL?

Hi there,
I know this is a cheeky request. Anyway, my organisation is using the
DocBook 5.1 betas in production, and we are keen to know if there is any
information regarding when the final release of the spec, and in
particular the XSL distribution which fully supports it, are likely to
be available.

Is there a known release timeframe?

We're using the assembly workflow to build documents so are hopeful that
at some point oXygen will be enhanced with an assembly manager so that
they're set up than at present. Assemblies work really well, but at
present we're building them manually.


Peter Lavin | 11 Aug 18:53 2014

two date entries in EPUB package.opf file


I'm using the the 1.78.1-ns style sheets to create an EPUB.

Within the tag I want to include both a copyright.year tag and a pubdate tag--publication dates are quite distinct from copyright years.

When validating using Epubcheck Version 3.0.1 I get the following error:

ERROR: docbook.epub/OEBPS/package.opf(19,14): element "dc:date" not allowed here

Two date entries are created in the package.opf file, one resulting from the pubdate tag and one from the copyright.year tag.

<meta property="dcterms:date">2014-09-01</meta>
<meta property="dcterms:date">2014</meta>
This seems to violate the EPUB requirement that there be only one DCMES date element. This is easy enough to fix after the fact but I don't see an easy workaround. Any suggestions?



Peter Lavin
Telephone:      1 416 461 4991
Mobile:            1 416 882 9194
Skype:             peter.lavin
(GMT -05:00 Canada/US Eastern)
Ken Morse | 10 Aug 18:56 2014

How to customize a template from division.xsl?

I'm trying to customize the book template from the dvision.xls stylesheet and run into an error for xsltproc. At this point, I'm not even changing the template, but simply putting a copy of it in my customization file produces the error, "I/O error : Is a directory" (happens when chunking the index.html file).

<xsl:template match="book">
  <xsl:call-template name="id.warning"/>

    <xsl:apply-templates select="." mode="common.html.attributes"/>
    <xsl:call-template name="id.attribute">
      <xsl:with-param name="conditional" select="0"/>

    <xsl:call-template name="book.titlepage"/>

    <xsl:apply-templates select="dedication" mode="dedication"/>
    <xsl:apply-templates select="acknowledgements" mode="acknowledgements"/>

    <xsl:variable name="toc.params">
      <xsl:call-template name="find.path.params">
        <xsl:with-param name="table" select="normalize-space($generate.toc)"/>

    <xsl:call-template name="make.lots">
      <xsl:with-param name="toc.params" select="$toc.params"/>
      <xsl:with-param name="toc">
        <xsl:call-template name="division.toc">
          <xsl:with-param name="toc.title.p" select="contains($toc.params, 'title')"/>


Is this likely a problem with precedence? If so, any idea what I need to do to be able to include this template in my customization layer?

BTW, I'm using the 1.78.1 stylesheets.


Phillip Kent | 8 Aug 16:23 2014

Saxon 9 (free HE version) and DocBook XSL Saxon extensions: Compatible and working?

Hello all,

can anyone confirm whether the Saxon extensions jar (I have tried
saxon65.jar in DocBook XSL 1.78.1) is compatible with Saxon 9HE ?

I just tried it in order to use the colwidth option for tables and got
the error 'No adjustColumnWidths function available', but I think I
have got my classpath correct.

(I had it like this in a bash shell script (with $1 = the filename to process):
java -cp ~/saxon/saxon9he.jar:~/saxon/DocBook/saxon65.jar
net.sf.saxon.Transform -s:$1.xml

On the other hand, I installed Saxon 6.5.5 and the docbook-saxon
package from the Linux Ubuntu repository, and that works fine.

Thanks Phillip