For the sources for an installation, many (hmm, maybe all of them) are acronyms.
An abbreviations document provides the expansion of the acronyms, plus lots and lots of unrelated acronyms.
When we use the acronym in the exported product, we should provide the expanded version as a tooltip. I guess the HTML <abbr> is the correct way of handling this, with the expanded version in the title.
Aah, there is a deeper integration here. I wish us to provide the document author with a drop-down list of source names. These will partially come from this list. So, I guess we have to:
walk the data, collate a list of all of the unique source fields
check we have abbreviation expansions for all of them - find the answers if we don't
collate this list of items in some DITA construct, then use it for the name field in tonal entities.
IanMayo
commented
7 months ago
For the
sourcesfor aninstallation, many (hmm, maybe all of them) are acronyms.An abbreviations document provides the expansion of the acronyms, plus lots and lots of unrelated acronyms.
When we use the acronym in the exported product, we should provide the expanded version as a tooltip. I guess the HTML
<abbr>is the correct way of handling this, with the expanded version in thetitle.Aah, there is a deeper integration here. I wish us to provide the document author with a drop-down list of source names. These will partially come from this list. So, I guess we have to:
namefield intonalentities.