OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [docbook-apps] acronyms, abbreviations, definitions

On Tue, 16 Nov 2010 19:38:51 +0000
"Rowland, Larry" <larry.rowland@hp.com> wrote:

> Actually, if you read the entire message, I was not suggesting that
> the rendered document have the content in a different location, I was
> suggesting that there was already markup available to represent the
> binding of the expansion to the acronym or abbreviation.  I am well
> aware that the rendered content has to have the expansion information
> attached to the element itself.
> I still feel that centrally locating the association is preferable in
> a modern document that is potentially delivered via the Web with
> entry points that may be based on search results or other
> non-narrative paths through a document.  Centrally locating the
> associated expansion reduces redundant coding.

But this isn't a glossary entry Larry? It's semantically wrong IMHO.

> > The glossentry element includes acronym and abbrev as valid
> > children.  This is where it might be best to link the expansion of
> > the acronym or abbreviation to the acronym or abbreviation (the
> > expansion is in the glossterm). 
> try it, with your eyes closed. This doesn't work Larry.
> Go through the motions compared with the inline acronym expansion.
> The expansion needs to be with the acronym, so that a tts
> app can read the acronym and its expansion together.



Dave Pawson

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]