Dennis Rautenberg | 25 Jul 13:03 2016

TOC broken after chunking

i try to generate a webhelp documentation.
the output should be chunked into different folders and filenames.
However, there is a bug open since 2011:
So i can't use it.

Is there any known workaround for that problem?


Kind Regards,
Dennis Rautenberg
Joseph Mingrone | 17 Jul 03:12 2016

validating individual files in a document


I'm working on setting up on-file-fly validation of FreeBSD documentation in
Emacs with nxml-mode.  I've configured Emacs/nmxl-mode to use FreeBSD's nearly
DocBook 5.0 compact relax NG schema.  Everything is working well, but there is
one issue that I am stumped on.  If I am working on a file (e.g. a chapter) that
is included in a main document (book) and that file uses project-specific
entities, the document will not validate.  I can put a DTD at the top of the
file with the entities, and it will validate, but that's clearly the wrong thing
to do since the book file already has a DTD.





Tree for FreeBSD's documentation:

Book file:
Chapter file: editor-config/chapter.xml, which is included in book.xml

The book is glued together with the Makefile there.  There are a few layers of
includes, which eventually pulls in the .ent files:

The compact relax NG schema:
(Continue reading)

Pc Thoms | 12 Jul 14:49 2016

DocBook Publisher - stagedir

I'm using the following to Xinclude several plays into one larger document, with OxygenXML 18. 

<?xml version="1.0" encoding="UTF-8"?>

<part xmlns="" xmlns:xlink="" version="5.0" remap="Play">

However, the stagedir and inlinestagedir elements do not validate.
I am using <para remap="stagedir"> as a work around.

Changing the <book/> to 
<part xmlns="" xmlns:xlink="" version="5.0" remap="PLAY"> 
was easy - all other elements remained the same, and prefaces, etc., stay as they are.

With thanks Paul
David Cramer | 22 Jun 22:10 2016

Re: [WebHelp] Language support for search

On 6/22/16 1:31 PM, Jan Tosovsky wrote:
> looking into the language support I can see only en/es/jp stopwords and
> de/en/fr stemmers:
> Has anybody implemented additional ones?
> In foreseeable future I'd like to cover also pt/it/cs/nl. I have some ideas,
> based on lucene analyzers, but why not use something existing ;-)

Hi Jan,

Your post prompted me to look at the Porter stemmer site to see if other
stemmers had been implemented in JavaScript:

While there, I noticed a link to the Urim project which appears to have
a number of stemmers in JavaScript:

Perhaps those could be adapted to work in webhelp.

Jan Tosovsky | 22 Jun 20:31 2016

[WebHelp] Language support for search

Dear All,

looking into the language support I can see only en/es/jp stopwords and
de/en/fr stemmers:

Has anybody implemented additional ones?

In foreseeable future I'd like to cover also pt/it/cs/nl. I have some ideas,
based on lucene analyzers, but why not use something existing ;-)


Mark Craig | 22 Jun 08:46 2016

Profiling/conditional text based on document context?


We use profiling/conditional text already at build time and it works fine.

What is the right way to set up conditional text to have the condition depend on the document context?

In other words, if the document is included in book 1, exclude this and include that. If the document is included in book 2, include this and exclude that.

Here's a simplified example, a common section XIncluded in two different release notes books:

<?xml version="1.0" encoding="UTF-8"?>
This file is included in both release notes in the same doc set.
Both sets of release notes are built *at the same time*.
That is, profiles depend on the document, not on the build.
<section xml:id="whats-new"
xmlns="" version="5.0" xml:lang="en"
<title>What's New</title>

This release includes the following new features:

<listitem><!-- Make this appear only in standard edition release notes. -->
A feature that is only in the standard edition of the product

<listitem><!-- Make this appear only in OEM edition release notes. -->
A feature that is only in the OEM edition of the product

<listitem><!-- Make this appear in both release notes. -->
A feature that is in both standard and OEM editions

The first item should be included in the standard edition release notes and excluded from the OEM edition release notes.

The second item should be excluded from the standard edition release notes and included in the OEM edition release notes.

The third item appears in both.

The whole doc set is built at the same time with the same configuration. In other words, the profiling conditions depend not on the build, but on the document context.

Thanks for your help.

stimits | 22 Jun 00:34 2016

fop/xsltproc, External SVG Issue

I'm struggling to embed SVG into a docbook5 document. I don't know if this is an issue of how I'm coding, or if this is an issue with the tools being used...any advice on solving this is welcomed.
I am using xsltproc with docbook5 docbook.xsl to produce a ".fo" file (Linux o/s), with the original XML validated error free under both xmllint and jing. I am thing using fop to create a number of output formats from the ".fo", pdf, rtf. The section of code with the svg being added refers to an external file, and in no case does any error or warning ever show up. Here's the sample code:
<!DOCTYPE book [
<!ENTITY version "0.1 unreleased">
<book xmlns=""
      xmlns:xi="" version="5.0">
                <imagedata align="left" format="svg" fileref="/somewhere/content/by-sa.svg"/>
                <phrase>CC BY-SA License</phrase>
                <para>This document is licensed under Creative Commons BY-SA License</para>
I have tried the fileref using full path, relative path, so on. There is never a complaint, the svg file itself displays and apparently is valid under a number of svg apps, and everything else shows up as expected. I have even tried intentionally making a very impossible and invalid file path, I cannot get a complaint from any of the tools. Am I using the XML wrong, or are my tools missing something under valid code?
Hussein Shafie | 21 Jun 11:21 2016

[ANN] Attractively priced XMLmind DocBook Editor; free Personal Edition

XMLmind is happy to announce three new products: XMLmind DITA Editor[1],
XMLmind DocBook Editor[2], XMLmind XHTML Editor[3].
These products are attractively priced, “special editions” of
XMLmind XML Editor v7. Because they focus on a single class of
documents, these specialized editors are slightly faster and simpler
to use than XMLmind XML Editor. More information in
"Which editor to choose?"[4].

A Personal License[5] is now available for XMLmind XML Editor,
XMLmind DITA Editor, XMLmind DocBook Editor and XMLmind XHTML Editor.
This makes our four editors free to use by many persons and
organizations. More information in "Which license to choose?"[6].

The Personal Editions of XMLmind XML Editor, XMLmind DITA Editor,
XMLmind DocBook Editor and XMLmind XHTML Editor may be freely
downloaded from this page[7].

New version 7.0 also has substantial enhancements and a number of bug
fixes. All these enhancements aim to make our XML editors simpler and
more straightforward to use.



More information in
Peter Lavin | 18 Jun 19:05 2016

PHP processing instructions


I'm using the 1.79.1 onechunk.xsl transformation style sheets with PHP
processing instructions. If I use the HTML onechunk.xsl file in my
customization level, a "?" is required immediately before the closing
processing instruction tag. For example:

<xsl:processing-instruction name="php">
//PHP code here

This produces the correct opening and closing PHP tags. (<?php ... ?>)

If I use the _XHTML_ onechunk.xsl file and a terminating "?" the
output is as follows:

//PHP code

Note the duplicate "?". Is this expected?




Peter Lavin
Telephone:      1 416 461 4991
Mobile:            1 416 882 9194
Skype:             peter.lavin
(GMT -05:00 Canada/US Eastern)
Pc Thoms | 23 May 22:36 2016

Line Numbering with DocBook Publisher

I came across the above and am wonder if Line Numbering with DocBook Publisher is possible? Possible using the <line/> element, that is.

With thanks Paul
stimits | 9 May 23:02 2016

Docbook 5 Samples?

With previous help I was able to get a Makefile working for complete validation and publishing to xhtml, rtf, pdf, and ps.
Now I'm at a point where I can actually author in docbook 5. I'm hoping someone here can suggest an available docbook 5 example document which contains a large array of commonly used intent being to first drop it in with my Makefile to test a larger build (there are actually multiple ways to publish some formats), and second to see the appearance and compare appearance between different tool variants for formatting. Because docbook elements are about content instead of appearance, references on various docbook 5 tags do not show example display; I'd like to see practical examples of conversion from tags to appearance.