Thanks for the quick response; let's continue the discussion 'face to face' rather than in the group …
You explain that <glossref href="ONE.dita" keys="key_ONE"/> is strictly equivalent to: <topicref href="ONE.dita" keys="key_ONE" linking="none" print="no" toc="no" search="no"/> Read as such, I would hope that setting the print attribute in the glossref to yes would resolve the problem; but as you will already know, it doesn't. As for the suggested workaround, a blog posting about DITA glossaries <http://idratherbewriting.com/acronyms_and_glossary/> says By the way, you don't have to use either abbreviated-form or term to refer > to a glossary term. You could also just refer to it with an xref. > However, if you just use xref, no tooltip appears when you mouse over the > link. Hence this method isn't recommended. > The tooltip is exactly what we want to deliver! With tooltips, our online helps can support both experienced users who don't need to look up definitions and new/occasional users who are less confident, and a colleague has already assembled a dictionary with 475 definitions we would like to deliver. I don't mind having to add/change attributes for each definition, if that will mean we get the tooltips; is there any chance ditac might deliver them in the future? N [ps] the colleague who assembled the dictionary is now decidedly a DITA convert, finds XML Mind an excellent tool and has even – what her secret is I don't know – persuaded her boss to let her hire two more technical writers so they can migrate existing content to DITA On Wed, Jul 26, 2017 at 10:44 AM, Hussein Shafie <[email protected]> wrote: > In case you are still using XXE/ditac... > > See very last limitation in http://www.xmlmind.com/ditac/_ > distrib/doc/manual/limitations.html > > --- > * Convenience element <glossref> (http://docs.oasis-open.org/di > ta/dita/v1.3/os/part2-tech-content/langRef/technicalContent/glossref.html) > cannot be used with ditac without setting some of its attributes. Example: > > <glossref href="ONE.dita" keys="key_ONE"/> > > is strictly equivalent to: > > <topicref href="ONE.dita" keys="key_ONE" linking="none" print="no" > toc="no" search="no"/> > > Notice default attribute print="no". Therefore, when generating PDF, such > <glossref> is discarded at a very early stage by ditac. The consequence is > that each occurrence of <abbreviated-form keyref="key_ONE"/> will cause > ditac to report a "cannot resolve keyref" warning. The workaround is to > simply avoid using <glossref> and to stick to <topicref> with a @keys > attribute. > --- > > > On 07/26/2017 10:27 AM, [email protected] [dita-users] wrote: > >> >> >> Managed to get the hang of keydef/keyref, after a bit of patient >> experiment, but I'm still having problems with the glossref mechanism. >> >> >> in ditamap >> <glossref href="accord_def.dita" keys="a001"/> >> >> in topic glossTest.dita >> Lorem ipsum dolor sit amet, consectetur adipiscing elit glossref to >> <term keyref="a001"/> >> >> in glossentry accord_def.dita >> <glossentry id="a001"> >> <glossterm>accord</glossterm> >> <glossdef><p>Informations spécifiques au moyen de paiement carte >> Accord.</p></glossdef> >> </glossentry> >> >> in output >> Lorem ipsum dolor sit amet, consectetur adipiscing elit glossref to >> {nothing} >> >> >> I'm hoping it's a simple error that someone can identify and clarify! >> thanks in advance. >> >> >>
-- XMLmind DITA Converter Support List [email protected] http://www.xmlmind.com/mailman/listinfo/ditac-support
