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

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita-translation message

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


Subject: FW: Re: Acronym samples




JoAnn T. Hackos, PhD
President
Comtech Services, Inc.
710 Kipling Street, Suite 400
Denver, CO 80215
303-232-7586
joann.hackos@comtech-serv.com
joannhackos Skype
www.comtech-serv.com

-----Original Message-----
From: Bruce Esrig [mailto:esrig-ia@esrig.com] 
Sent: Tuesday, January 22, 2008 2:02 AM
To: JoAnn Hackos
Subject: Fwd: Re: Acronym samples

Copy for you of the earlier message to Robert.

Bruce

>Date: Sat, 19 Jan 2008 23:41:31 -0500
>To: Robert D Anderson <robander@us.ibm.com>
>From: Bruce Esrig <esrig-ia@esrig.com>
>Subject: Re: Acronym samples
>Cc: <bhertz@sdl.com>, "Bryan Schnabel" <bryan.s.schnabel@tek.com>, 
>Charles_Pau/Cambridge/IBM%Lotus 
><Charles_Pau/Cambridge/IBM%Lotus@us.ibm.com>,
<christian.lieske@sap.com>, 
><dpooley@sdl.com>, <esrig-ia@esrig.com>, <fsasaki@w3.org>, 
><rfletcher@sdl.com>, <ishida@w3.org>, <rmraya@maxprograms.com>, 
><tony.jewtushenko@productinnovator.com>, <KARA@CA.IBM.COM>, 
><ysavourel@translate.com>, Erik Hennum <ehennum@us.ibm.com>, Michael 
>Priestley <mpriestl@CA.IBM.COM>, jogden@ptc.com
>
>Looks great, Robert,
>
>The new structure really separates the issues cleanly:
>  - <glossentry> to represent an entry
>  - SurfaceForm and Alt to represent ways of expanding an acronym
>
>1. The <abbreviated-form> is only one way to display an acronym. Is the

>control of the output form left up to policies encoded in the
production 
>system? I.e. "First occurrence displays the SurfaceForm", "Subsequent 
>occurrences display the abbreviated form", "alt attributes display the 
>Alt", "Titles ... (to be determined)".
>
>Or are there additional controls for authors? "Display the abbreviated 
>form here" (in one title), "Display the SurfaceForm here" (in a title
at 
>lower heading level, for example).
>
>2. Was a decision made that the headword in the glossary (used to 
>alphabetize the entry, and to enter it) would always be the abbreviated

>form? For some glossaries, the alt form might trigger a separate
listing 
>with the alt form as a headword. This could even be done under control
of 
>the glossentry itself, in case authors discover that certain entries
are 
>often looked up in their expanded form. It might be better to offer a 
>mechanism for dual entries rather than rely on conref.
>
>Sorry, I can't copy the main list,
>
>Bruce
>
>At 05:54 PM 1/18/2008, Robert D Anderson wrote:
>
>>Hi everybody -
>>
>>In preparation for Monday's acronym discussion, I took two examples
from
>>our original proposal, and placed them side by side with matching
examples
>>from the merged acronym/glossary proposal. My hope is that this makes
it
>>easier to compare the actual markup and to get a clear picture of what
>>authors or translators will actually see. This should be handy to look
at
>>when discussing differences between the two during our meeting.
>>
>>If I've left something out or gotten an element name wrong in samples
for
>>either proposal, that's my fault, and not intentional. If something is
>>wrong, please let me know, and I'll try to get a new version out
before our
>>meeting.
>>
>>(See attached file: acronymproposals.html)
>>
>>Thanks -
>>
>>Robert D Anderson
>>IBM Authoring Tools Development
>>Chief Architect, DITA Open Toolkit
>>(507) 253-8787, T/L 553-8787 (Good Monday & Thursday)



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