After looking at your sample ditamap, we have realized that the
following way of authoring a glossary is absolutely not supported by
XMLmind DITA Converter, the DITA processor included in XMLmind XSL Utility:
---
<glossarylist>
<topicref href="glossary_entry1.dita"/>
<topicref href="glossary_entry2.dita"/>
<topicref href="glossary_entry3.dita"/>
<topicref href="glossary_entry4.dita"/>
<topicref href="glossary_entry5.dita"/>
</glossarylist>
---
Why that? Well...it's a basically an omission in our implementation!
Therefore this is not a simple bug we could fix today in order to very
quickly send you a patch. It will take some time to support this style
of glossarylist. Sorry for that.
Meanwhile, we suggest A) or B):
Workaround A)
-------------
1) to move your glossary out of <booklists>, that is:
---
<backmatter>
<booklists>
<figurelist/>
<tablelist/>
<glossarylist>
<topicref href="glossary_app_context.dita"/>
</glossarylist>
<indexlist/>
</booklists>
</backmatter>
---
becomes:
---
<backmatter>
<topicref href="glossary.dita"/>
<booklists>
<figurelist/>
<tablelist/>
<indexlist/>
</booklists>
</backmatter>
---
2) to group all your <glossentry>s into a single <glossgroup>. Let's
suppose file glossary.dita contains such <glossgroup>:
---
<!DOCTYPE glossgroup PUBLIC "-//OASIS//DTD DITA Glossary Group//EN"
"glossgroup.dtd">
<glossgroup id="glossary_app_context">
<title>Glossary</title>
<glossentry id="glossentry-app_context-1" xml:lang="de-DE">
<glossterm>APP_CONTEXT</glossterm>
<glossdef>Definition...</glossdef>
</glossentry>
<glossentry id="glossentry-app_context-2" xml:lang="de-DE">
<glossterm>APP_CONTEXT</glossterm>
<glossdef>Definition...</glossdef>
</glossentry>
</glossgroup>
---
Workaround B)
-------------
Alternatively, what follows seems to work too:
---
<backmatter>
<booklists>
<figurelist/>
<tablelist/>
<glossarylist href="glossary.dita"/>
<indexlist/>
</booklists>
</backmatter>
---
Notice that here too, all your <glossentry>s are grouped into a single
<glossgroup>.
On 10/08/2012 11:05 AM, Frank Glaes wrote:
> attached is a simple example.
> If you convert the file "Handbuch.ditamap" as provided everything works fine
> and you get the word file.
>
> If un-commenting line 29 you get an error during conversion.
> The remaining .fo file is also in the attached .zip file.
>
> I also attach a screenshot of the converter.
>
> So the problem seems to be in the glossary stuff.
>
On 10/05/2012 06:32 PM, Frank Glaes wrote:
> I get the following error:
>
> …
>
> Transforming ">8 cut …Betriebshandbuch.ditac" to ">8 cut
> …Betriebshandbuch.fo" using
> V:\Tools\xslutil_pro-4_7_0\addon\config\dita\xsl\fo\fo.xsl...
>
> fatal error reported by the XSLT engine:
>
> A sequence of more than one item is not allowed as the first operand of 'eq'
> (36, 39) ; SystemID:
> file:/V:/Tools/xslutil_pro-4_7_0/addon/config/dita/xsl/fo/pagination.xsl;
> Line#: 798; Column#: -1
>
> cannot transform ">8 cut …
>
> java.lang.RuntimeException: Conversion "ditaToDocx" has failed with exit code
> 5.
>
> +---------------------------------------
>
> | com.xmlmind.xslutil.ConvertTask.doRun1(ConvertTask.java:182)
>
> | com.xmlmind.xslutil.ConvertTask.doRun(ConvertTask.java:133)
>
> | com.xmlmind.xslutil.ConvertTask.run(ConvertTask.java:112)
>
> | java.lang.Thread.run(Unknown Source)
>
> +---------------------------------------
>
>
>
>
>
> What could be the reason for that?
>
> I’m using glossary in the backmatter. Could that be the problem?
>
> I remember similar problems in the past and removed the glossary. But DOTA OT
> has no problems creating PDF.
>
>
>
> Any idea?
--
XMLmind FO Converter Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/xfc-support
