#1294 glossary.collection not processed correctly

output: HTML
pending-invalid
XSL (1066)
5
2013-08-29
2013-03-08
No

I set the value of glossary.collection param of a Docbook to XHTML transform to the path of a glossary file that looks like:

<glossary role="auto" xmlns="http://docbook.org/ns/docbook" version="5.0">
<glossdiv><title>X</title>
<glossentry xml:id="entry1">
<glossterm>stratégie</glossterm>
<glossdef>
<para> Mon test ITIL </para>
</glossdef>
</glossentry>
<glossentry xml:id="entry2">
<glossterm>Rapport</glossterm>
<glossdef>
<para annotations="BringhtPoint Consulting Inc">On utilise surtout un rapport
pour examiner des données brutes dans un format lisible. </para>
</glossdef>
</glossentry>
</glossdiv>
</glossary>

I insert references to the glossary terms in a Docbook document, for example:

<glossterm linkend="entry2">a term here</glossterm>

<xref linkend="entry1"/>

I transform the Docbook document containing these references to XHTML but the glossary definitions are not added to the XHTML output and the links to the glossary definitions do not work.

Setting the glossterm.auto.link param to 0 or 1 makes no difference in the output. I use Docbook XSL 1.77.1 and the Saxon 6.5.5 processor.

Discussion

  • Sorin Ristache

    Sorin Ristache - 2013-03-08

    An additional problem is that in the XHTML output the Table of Contents contains a broken link to a Glossary section, that is there is no output file with the glossary definitions that the references should point to.

     
  • David Cramer

    David Cramer - 2013-03-08

    I believe that the current auto glossary mechanism actually matches the term rather than on the id. So in your example if you did: "<para>Votre <glossterm>stratégie</glossterm> n'est pas mal.</para>" it would work.

    You can also do "<para>Vos <glossterm baseform="stratégie">stratégies</glossterm> n'est pas mal.</para>" where it would match based on the value of baseform instead of the content of the tag. Note that line breaks in the term can cause it not to match.

    Personally, I think it should work based on id if ids exist and then fall back to baseform, then to the content of the tag (with space normalized), so there are at least limitations here that should be addressed.

     
  • Robert Stayton

    Robert Stayton - 2013-08-29
    • status: open --> pending-invalid
    • assigned_to: Robert Stayton
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks