Janice Manwiller | 30 Mar 18:00 2015

WebHelp display issues - contents expand/collapse icons, intra-topic links

I've run into a couple of minor issues with how the DocBook WebHelp is displayed. Has anyone else seen either of these, or have any fixes?

Expand/collapse icons in the contents become out of sync

If you display the WebHelp, expand and collapse nodes in the table of contents, go to another page, then return to the WebHelp, the expand/collapse icons can get out of sync with the expand/collapse status of the nodes. You can see the issue in the attached image.

Links within a topic do not jump to the target

I have a WebHelp topic that contains a link to a target ID (on a bridgehead) within that topic. When the topic displays, the link is visible, but the target is further down and so not immediately visible. When you click the link, it does not jump to the target. However, if you right click and open the link in a new tab, it opens to the correct location. I've tried using both xref and link, and get the same results.



To unsubscribe, e-mail: docbook-apps-unsubscribe <at> lists.oasis-open.org
For additional commands, e-mail: docbook-apps-help <at> lists.oasis-open.org
Sascha Manns | 30 Mar 16:39 2015

Header and Footerlines in article

Hello List,

actually it looks like after processing DocBook to PDF the result has on the top and on the bottom a vertical line.
Does anyone knows where these lines are coming from? I would like to doesn't use it on the titlepage. I read http://www.sagehill.net/docbookxsl/HTMLTitlePage.html but there i haven't found anything about them.

greetings Sascha
-- Yours sincerly Sascha Manns
DeanNelson | 24 Mar 02:07 2015

Inserting ENTITYs without removing the DOCTYPE in Docbook files

I am trying to resolve/replace the ENTITYs in my Docbook files without removing the DOCTYPE declaration. I tried using XMLLINT:
    xmllint --noent --dropdtd -o outfile.xml infile.xml
but this removed the DOCTYPE line along with resolving the ENTITYs. So if I don't use the --dropdtd then I get all of the ENTITYs brought in by the ENTITY line in the DOCTYPE.
Here is the snippet of XML that I start with:
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.docbook.org/xml/4.5/docbookx.dtd"[
<!ENTITY % my-defs SYSTEM "my-defs.mod">        %my-defs;
<chapter id="introduction-and-overview">
 <title>Introduction and Overview</title>
   &CORP_NAME; Veneer Testers are high-speed, production-line
   testing machines for precision grading of wood veneer. The
   different models of &CORP_NAME; Veneer Testers measure
   different properties (or combinations of properties) of
   veneer in order to grade it.
Here is what I am getting now with the --dropdtd

<?xml version="1.0" encoding="utf-8"?>
<chapter id="introduction-and-overview">
 <title>Introduction and Overview</title>
   Metriguard Veneer Testers are high-speed, production-line
   testing machines for precision grading of wood veneer. The
   different models of Metriguard Veneer Testers measure
   different properties (or combinations of properties) of
   veneer in order to grade it.
Here is what I want:
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.docbook.org/xml/4.5/docbookx.dtd"[
<!ENTITY % my-defs SYSTEM "my-defs.mod">        %my-defs;
<chapter id="introduction-and-overview">
 <title>Introduction and Overview</title>
   Metriguard Veneer Testers are high-speed, production-line
   testing machines for precision grading of wood veneer. The
   different models of Metriguard Veneer Testers measure
   different properties (or combinations of properties) of
   veneer in order to grade it.
My question is has anyone dealt with this before? and how?
Dean Nelson
DeanNelson | 20 Mar 07:16 2015

Getting a list of XInclude'd files

I'm sure this is a pretty common issue? I need to get a list of all of my XIncluded files in a document.
I need to package up all of the Docbook files required for a particular document so I can send them off to the translators. The document is in a directory with many more Docbook files that are not part of that particular document, so grep'ing would not work well for a list.
I have tried a few ways but I thought that I would ask on this list to see if any of you have a quick and easy way to process a list. I usually use XSLTPROC or Saxon as a processor (Windows and Linux).
Any ideas?
Dean Nelson
Flavia Majlis | 16 Mar 02:56 2015

processing-instruction does not work within <link> tag

I am using libxml2-2.7.8 and docbook-xsl-1.78.1

In my customization layer, I have a processing instruction which consists of a simple text string:

<xsl:template match="processing-instruction('brand')">ABC</xsl:template>

and in my .xml I have a link:

<link linkend='my_section_id'>The brand is <?brand?></link>

In the pdf output link I see: "The brand is ABC"
but in the html link text I see "The brand is"

In most of the rest of the html output the instruction is being processed and <?brand?> is replaced by "ABC". 

Any ideas why the processing-instruction('brand') is not being processed within the <link> tag for the html output?

Flavia Majlis,
MSc, Computer Science, McGill University
BFA, Photography, Concordia University


Erik Leunissen | 13 Mar 18:58 2015

A docbook-xsl parameter "bridgehead.renderas"


As it happens, I find myself repeatedly in the situation where I want to 
use bridgeheads.

In all of these cases I want all bridgeheads throughout the document to 
be rendered in the same way; as a section at a specific level (e.g. 
sect5). [*]

The facility to customize this is the renderas attribute to the 
bridgehead element.

In my use case, it strikes me as inapt to have to adjust that attribute 
in ever the same way for each instance of a bridgehead in the document. 
It seems logical/practical to have a docbook-xsl parameter (e.g. 
"bridgehead.renderas") which handles this at at the document level.

The docbook-xsl stylesheets do not currently provide such a facility. 
Well, I guess that amounts to a Feature Request ...

Anything wrong with this idea?


Erik Leunissen.

[*] I'm producing PDF output using docbook-xsl - xsltproc - fop
Erik Leunissen | 8 Mar 22:29 2015

Problem customizing appendix title (for PDF)

Hi all,

I want the label of an appendix in an article to show up in a final PDF
as follows:

Bijlage 1. SomeDutchTitle

(The word "Bijlage" is Dutch for "Appendix".)

So the text "Bijlage" is to be prepended to the appendix number.

Chapter 9 of the book "Docbook XSL, The complete
Guide", pages 105 and 106, covers this customization. Or online:


It reads:

<l:context name="title">
   <l:template name="appendix" text="Appendix %n. %t"/>

Below, you find a minimal docbook xml source. Also a minimal docbook xsl
file, analogous to the above customization in English, which I applied
using xsltproc. Finally, I used fop to generate
the final PDF (which seems to me irrelevant to the issue).

I fail to produce output that has *any* text prepended to the appendix's
number (i.e. even regardless the Dutch language).

Does anybody see what I'm doing wrong?

Thanks in advance for any insight,

Erik Leunissen

# Docbook XML source
<?xml version="1.0" encoding="UTF-8"?>
<article version="5.0" xmlns="http://docbook.org/ns/docbook"






     <para>Some section text.</para>

     <title>My appendix</title>


# Docbook XSL
<?xml version='1.0'?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"

<!-- base stylesheet -->

<xsl:param name="appendix.autolabel" select="1"/>
<xsl:param name="l10n.gentext.language">nl</xsl:param>
<xsl:param name="local.l10n.xml" select="document('')"/>
<l:i18n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0">
   <l:l10n language="nl">
     <l:context name="title">
       <l:template name="appendix" text="Bijlage&#160;%n.&#160;&#160;%t"/>


Alan Oehler | 6 Mar 23:13 2015

Using custom fonts

I created a fop config file to register Trebuchet as my basic body font and Consolas as my monotype font. Worked beautifully – except it seems like all the places where I'd used <emphasis>...</emphasis> are no longer italicized, and where I'd used <emphasis role="bold">...</emphasis> are no longer bolded (emboldened?).

I added all four variants of both fonts (normal, italic, bold and bold italic). Is there some other detail I'm missing?




Alan C. Oehler
Senior Technical Writer

Phone: 650-919-8856 | Email: aoehler <at> instartlogic.com 
Instart Logic | 450 Lambert Ave, Palo Alto, CA 94306 | instartlogic.com

Shikareva, Ekaterina | 5 Mar 08:19 2015

Eclipse Help generation - anchor IDs



I generate Eclipse HTML Help from my DocBook files with xsltproc, and every generation leads to attribute (ID) changes in anchor tags. Because of this we get a lot of warnings during code reviews.

Our current solution is to mark such changes as unimportant in Beyond compare, but is there a way to minimize anchor ID changes during HTML files generation?



Kind regards,

Ekaterina Shikareva

Senior Technical Writer

Luxoft Russia


Skype: maymakayu 




This e-mail and any attachment(s) are intended only for the recipient(s) named above and others who have been specifically authorized to receive them. They may contain confidential information. If you are not the intended recipient, please do not read this email or its attachment(s). Furthermore, you are hereby notified that any dissemination, distribution or copying of this e-mail and any attachment(s) is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by replying to this e-mail and then delete this e-mail and any attachment(s) or copies thereof from your system. Thank you.
Sascha Manns | 25 Feb 15:47 2015

glossterm bold

Hello list,

actual i'm trying to make (for fo output) all glossterms in glossary/glossentry/glossterm in bold.

I tried out:

<xsl:template match="glossterm">
            <xsl:call-template name="inline.boldmonoseq"/>

<xsl:template match="glossterm">
        <fo:inline font-weight="bold">
            <xsl:call-template name="inline.charseq"/>

But it looks like it doesn't matches while rendering.

Maybe i miss anything?
-- Yours sincerly Sascha Manns --------------------------------- XCOM AG Qualitätsmanagement Banksystem Backend Rechnungswesen, Meldewesen, Steuern Rennweg 60 Haus 2 56626 Andernach Telefon +49 2632 9899-158 Telefax +49 2632 9899-010 Sascha.Manns <at> xcom.de http://www.xcom.de *** XCOM AG Legal Disclaimer *** Diese E-Mail einschliesslich ihrer Anhaenge ist vertraulich und ist allein für den Gebrauch durch den vorgesehenen Empfaenger bestimmt. Dritten ist das Lesen, Verteilen oder Weiterleiten dieser E-Mail untersagt. Wir bitten, eine fehlgeleitete E-Mail unverzueglich vollstaendig zu loeschen und uns eine Nachricht zukommen zu lassen. This email may contain material that is confidential and for the sole use of the intended recipient. Any review, distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Hauptsitz: Allee 8, D-47877 Willich, USt-IdNr.: DE 812 885 664 Kommunikation: Telefon +49 2154 9209-70, Telefax +49 2154 9209-900, www.xcom.de Handelsregister: Amtsgericht Krefeld, HRB 10340 Vorstand: Dirk Franzmeyer, Marco Marty, Dirk Werner, Sascha Bochartz Vorsitzender des Aufsichtsrates: Stefan H. Tarach
Attachment (smime.p7s): application/pkcs7-signature, 5223 bytes
Thomas Schraitle | 17 Feb 10:27 2015

Strategies for Migrating DocBook Customization in a Mixed DB4/5 Environment?

Hi DocBook users,

currently, I'm trying to migrate our old DocBook 4 sources to version
5. This is pretty straightforward and can be done with some XSLT magic.
The markup side is also well covered in the "DocBook 5.0 Transition

However, during this transition, some documents will be kept in DocBook
4. So we end up with a mixed setup for both versions.

(Of course, I could feed my new DocBook 5 sources into my existing XSL
customizations. This "works", but it takes too much time because of the
internal convertion of DocBook 5 to DocBook 4.)

As such, it would be nice to have a clear separation: use the normal,
non-namespace variant for version 4 and the namespace-aware for
version 5.

However, we have some some hefty DocBook XSL customizations; a
"DocBook XSL Transition Guide" would be helpful. :)

How would you deal with such migration of "old" DocBook 4 XSL
customization layers?

Any thoughts are highly appreciated! Thanks! :-)

[1] http://docbook.org/docs/howto/


    Thomas Schraitle