Hussein Shafie wrote:
> Bernd Kuemmerlen wrote:
>
>> The problem now is that I don't see a way of converting these
>> glossentries to:
>>
>> <glossentry>
>> <glossterm></glossterm>
>> <glossdef></glossdef>
>> </glossentry>
>>
>> which is what you want as a default most of the time.
>
>
> Select element glosssee and *replace* it by element glossdef. For this
> you need to use (rarely used) command Replace.
Thanks! I knew there had to be some way, but I missed this command entirely
> This was the right thing to do.
>
> You are not limited to a single elementTemplate, so why not also add:
>
> <elementTemplate name="see">
> <glossentry xmlns="">
> <glossterm></glossterm>
> <glosssee></glosssee>
> </glossentry>
> </elementTemplate>
>
> Notice the meaningful name and the absence of selectable="override".
Yes, I was thinking along these lines as well, thanks for confirming this.
> You cannot convert (i.e. using command Convert) the contents of a
> glosssee to a glossdef and vice-versa because these elements have very
> different content models.
OK, I understand now, the glosssee elements had the form
<glosssee>
some text
</glosssee>
and obviously this can not be converted to glossdef because PCDATA is
not allowed in glossdef.
> In practice, a glossdef is *semantically* a very different beast from a
> glosssee so this should not be very annoying.
No, with the two different templates, this works very well, and for the
rare cases where the transformation is needed, I think the "Replace" is OK.
Thank you very much for your help
Bernd
--
"The first discovery I'd like to present here is an algorithm for lazy
evaluation of research papers. Just write whatever you want and don't
cite any previous work, and indignant readers will send you references
to all the papers you should have cited." -- Paul Graham
