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


Help: OASIS Mailing Lists Help | MarkMail Help

dita-comment message

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

Subject: Re: [dita-comment] no support for <sup> and <sub> in some glossaryelements?

I can't speak to the design decisions behind the glossary markup, but it
does seem odd that the content model for e.g., glossAbbreviation does not
allow <ph>:

<!ENTITY % glossAbbreviation.content
                       "(#PCDATA |
                         %keyword; |
                         %term; |

Since <sup> and <sub> are specializations of <ph> they are excluded from
this content model.



On 2/9/11 4:29 PM, "Amber Swope" <amberswope@gmail.com> wrote:

> I need to indicate a chemical or equation ³formula² for a glossary term and
> the glossary elements that seem to be the most appropriate for this usage do
> not support the <sup> and <sub> elements:  <glossAbbreviation>,
> <glossAcronym>, <glossShortForm>, and <glossSynonym>.  For example, for the
> term ³water², the chemical expression is H2O; my first choice for capturing
> the expression is <glossShortForm>, but it doesnıt support <sub>. Another
> example is the term ³terminal velocity² with the equation symbol of Vt.
> Is there a specific reason for this limitation? Any suggestions for a
> workaround other than appropriating <glossProperty>? In these cases,
> <glossUsage> is already taken.
> Thanks, A
> Amber Swope
> dita specialist
> <dita strategies>
> 503.922.3038
> amberswope@gmail.com

Eliot Kimber
Senior Solutions Architect
"Bringing Strategy, Content, and Technology Together"
Main: 512.554.9368

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