On 11/05/2015 05:38 PM, Vic S. wrote:
I am working on a set of documents with a large number of glossary
items. I have therefore:
·created a series of glossary items,
·Referenced each glossary item and allocated each one a key using a
series of glosrefs in a sub ditamap.
·Referenced the glossary map from my main map using a mapref
·Referenced each glossary item using term or abbreviated-form in my text
The problem is that when I output to XHTML or to pdf, the terms are not
pulled forward into the output.
My glossary items include a gloss-acronym and a gloss-surfaceform element
I suspect I have got one of the output parameters set incorrectly. Can
you point me in the right direction.
[email protected] wrote:
What you do seems pretty advanced in terms of DITA glossary. I suspect that you
have found a bug.
Please send us all the DITA files needed to reproduce this problem. Your
description of the problem, while clear, is not sufficient to be able to help
you.
Vic S. wrote:
I cannot send you the original project files but I have created a simpler
example (see zipfile attached) that does not use a separate ditamap for the
glossary entries. It still displays the same behaviour.
I have used 2 methods to try and include the glossary term in the output text.
Method 1 uses the glosref element in the ditamap - the terms are not returned.
Method 2 uses the topicref element - the full glossary term is now returned for both
instances where the <abbreviated-form> is used. i.e. the full surface form and
acronym values of the glossary entry are ignored.
[email protected] wrote:
--> As surprising as it may be, the behavior of XMLmind DITA Converter
seems conforming to the DITA spec concerning glossref.
<glossref href="STE.dita" keys="key_STE"/>
is strictly equivalent to:
<topicref href="STE.dita" keys="key_STE" linking="none" print="no"
toc="no" search="no"/>
See the default attribute values of glossref in
http://docs.oasis-open.org/dita/v1.2/os/spec/langref/glossref.html
* print="no" implies that STE.dita is filtered out when you generate PDF.
* linking="none" implies that
<abbreviated-form keyref="key_STE"/>
does not link back to the glossary entry found in STE.dita.
As we understand it, glossref seems to be unusable because it has design
problems:
- Its required "keys" attribute is fine.
- The default values of linking, print, toc, search are not.
If you don't agree with this analysis, do not hesitate to point us to
the sections of the DITA 1.2 spec which contradict it.
--> This being said, there should be no such problems with:
<topicref href="STE2.dita" keys="key_STE2"/>
and:
<abbreviated-form keyref="key_STE2"/>
Well, in fact there are problems, because as you have found it, the text
pulled by XMLmind DITA Converter should be the glossSurfaceForm or the
glossAcronym and not the title of the glossentry.
These are limitations which we'll try to remove in the release of
XMLmind DITA Converter
--
XMLmind DITA Converter Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/ditac-support
