[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [dita-translation] DITA Translation Subcommittee
Chris, I'd like to add the glossary specification to the subcommittee agenda for 2007. We can make a proposal to the TC for the 1.2 specification or the 2.0, depending upon what is next. JoAnn 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: Chris Wong [mailto:cwong@idiominc.com] Sent: Thursday, January 04, 2007 1:52 PM To: Kara Warburton; Andrzej Zydron Cc: bhertz@sdl.com; Bryan Schnabel; charles_pau@us.ibm.com; christian.lieske@sap.com; dita-translation@lists.oasis-open.org; dpooley@sdl.com; dschell@us.ibm.com; esrig-ia@esrig.com; fsasaki@w3.org; Howard.Schwartz; ishida@w3.org; Jennifer Linton; JoAnn Hackos; mambrose@sdl.com; Nick Rosenthal; rfletcher@sdl.com; tony.jewtushenko@productinnovator.com; ysavourel@translate.com; melbyak@yahoo.com; sewright@neo.rr.com Subject: RE: [dita-translation] DITA Translation Subcommittee There already is a glossary topic in the draft DITA 1.1 proposal, but it's substantially stripped down compared to the proposal you pointed us to below. It consists of term/definition element pairs: no glossdetail. That's certainly a step up from <term>, but I don't think it's that useful from your perspective as a terminologist as there is no way to connect terms conceptually: it's lexicological rather than terminological. What are your thoughts on that? Sample markup from the DITA 1.1 draft (lang ref): <glossentry id="ddl"> <glossterm>Data Definition Language</glossterm> <glossdef>A formal language used for defining database schemas....</glossdef> </glossentry> Chris -----Original Message----- From: Kara Warburton [mailto:KARA@CA.IBM.COM] Sent: Thursday, December 28, 2006 10:29 AM To: Andrzej Zydron Cc: bhertz@sdl.com; Bryan Schnabel; charles_pau@us.ibm.com; christian.lieske@sap.com; Chris Wong; dita-translation@lists.oasis-open.org; dpooley@sdl.com; dschell@us.ibm.com; esrig-ia@esrig.com; fsasaki@w3.org; Howard.Schwartz; ishida@w3.org; Jennifer Linton; JoAnn Hackos; mambrose@sdl.com; Nick Rosenthal; rfletcher@sdl.com; tony.jewtushenko@productinnovator.com; ysavourel@translate.com; melbyak@yahoo.com; sewright@neo.rr.com Subject: Re: [dita-translation] DITA Translation Subcommittee Has anyone looked at the glossary specification proposal that I have had in the DITA queue for several years now? Here it is... comments are welcome, especially since, its been so long, it probably needs revising again... http://www.oasis-open.org/committees/download.php/15140/Issue14.html IBM has been waiting patiently for something like this to be introduced to DITA so that we have something more than definition list markup for glossary content. Kara Warburton IBM LanguageWare & Terminology Team Lead, Language & Data Integration 905-413-2170 IBM terminology: http://w3.ibm.com/standards/terminology LanguageWare: http://languageware.redirect.webahead.ibm.com/ My blog: http://blogs.tap.ibm.com/weblogs/page/kara@ca.ibm.com Andrzej Zydron <azydron@xml-intl .com> To JoAnn Hackos 12/28/2006 05:35 <joann.hackos@comtech-serv.com> AM cc dita-translation@lists.oasis-open.o rg, cwong@idiominc.com, mambrose@sdl.com, bhertz@sdl.com, Bryan Schnabel <bryan.s.schnabel@tek.com>, charles_pau@us.ibm.com, christian.lieske@sap.com, dpooley@sdl.com, dschell@us.ibm.com, esrig-ia@esrig.com, fsasaki@w3.org, rfletcher@sdl.com, "Howard.Schwartz" <Howard.Schwartz@trados.com>, Jennifer Linton <jennifer.linton@comtech-serv.com>, Nick Rosenthal <nick@salftrans.co.uk>, ishida@w3.org, tony.jewtushenko@productinnovator.c om, Kara Warburton/Toronto/IBM@IBMCA, ysavourel@translate.com Subject Re: [dita-translation] DITA Translation Subcommittee Hi JoAnn, As far as I can tell, there is no DITA element specifically designed for acronyms/abbreviations. Please correct me if I am wrong. Acronyms feature very often in technical documentation and their treatment in translation poses some interesting issues. I have the following proposal for the main DITA TC: A new <acronym> element that can occur anywhere within PCDATA. The acronym will have an 'id' attribute that will be the acronym itself, e.g. <acronym id="ABS"/>. The <acronym> element will be resolved via a conref attribute to the full acronym text, e.g. acronym id="ABS" conref="aconyms.dita#abs"/>. The entry in the aconyms.dita file will be: <acronym name="abs">Anti-lock Break System</acronym> At compose time, when you are putting together the publication you can print the full form the first time around, but in parentheses to get around any potential problems when translating into inflected languages: <p>The <acroym id="ABS" conref="aconyms.dita#abs"/> facility will prevent the car from skidding.</p> This will be published as: The ABS (Anti-lock Break System) facility will prevent the car from skidding. This is in reverse to what would normally be printed, e.g. Anti-lock Break System (ABS) But this is perfectly acceptable and gets around translation problems with inflected languages. Best Regards, AZ JoAnn Hackos wrote: > When: Occurs every Monday effective 1/8/2007 until 2/26/2007 from 9:00 > AM to 10:00 AM (GMT-07:00) Mountain Time (US & Canada). > > *~*~*~*~*~*~*~*~*~* > > DITA Technical Committtee teleconference USA Toll Free Number: > 866-566-4838 USA Toll Number: +1-210-280-1707 > PASSCODE: 185771/ > > This notice covers regular meetings through the end of February 2007. > -- email - azydron@xml-intl.com smail - c/o Mr. A.Zydron PO Box 2167 Gerrards Cross Bucks SL9 8XF United Kingdom Mobile +(44) 7966 477 181 FAX +(44) 1753 480 465 www - http://www.xml-intl.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you may not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. Unless explicitly stated otherwise this message is provided for informational purposes only and should not be construed as a solicitation or offer.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]