[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: DITA Translation Subcommittee: Agenda for 18 September
Agenda for
Monday 18 September
2006
11:00 am - 12:00 am Eastern
Standard Team DITA Technical Committee teleconference USA Toll Free Number:
866-566-4838
+1-210-280-1707
PASSCODE:
185771
I"m at the Best Practices conference in San Diego this week. Sorry to miss the meeting. JoAnn
Roll Call
Accept Minutes
from 11 September 2006 (enclosed for those who are not
TC members)
http://www.oasis-open.org/apps/org/workgroup/dita-translation/<http://ww
w.oasis-open.org/apps/org/workgroup/dita-translation/>
Attached for
non-members.
3) Review open action
items
--ACTION-- Next draft
of the best practice for legacy TM (Gershon Joseph)
CONTINUE.
--ACTION-- Nancy Harrison
to work on examples of multi-language documents this week and we'll formulate a
definition next meeting.
CONTINUE.
--ACTION-- Andrzej develop
a conref best practice document
CONTINUE.
4) Returning business:
4.1 Review and approve Gershon'a revision of the TM best practices
4.2 Review Andrzej's draft of the best practices on conref
4.3 Review
Rodolfo’s XLIFF article outline at the Heartsome wiki
address
http://www.heartsome.org/hswiki/DITA_XLIFF
If
anyone wants to add sections, comments or any idea, please go ahead and change
the wiki.
Other continued action items if
available.
New
Business:
none
JoAnn T. Hackos,
PhD
President
Comtech Services,
Inc.
303-232-7586
joann.hackos@comtech-serv.com
www.comtech-serv.com
JoAnn T. Hackos, PhD
President
Comtech Services,
Inc.
710 Kipling
Street, Suite 400
Denver CO 80215
303-232-7586
joann.hackos@comtech-serv.com
Many organizations have previously translated content that was authored in non-DITA tools (such as Word and FrameMaker). When migrating their legacy content into the new DITA authoring environment, what does the organization do about their legacy translation memory? This legacy translation memory (TM) was created with large financial investment that can't easily be thrown away simply because a new authoring architecture is being adopted. This article describes best practices that will help organizations to use their legacy TM for future translation projects that are authored in DITA, in order to minimize the expense of translating DITA-based content. Before we get into the details, let's define the terms used in the localization industry so that subsequent sections will be better understood.
This section describes the process at a high level that is independent of tools used and the features they support. If DITA content is stored on a file system or in a CMS that does not support TMX (or in a CMS that uses proprietary techniques to implement reuse and other features that would be lost by exporting to TMX), then proceed as follows:
This section describes the recommend approach when using tools that fully support DITA and TMX. When your DITA content is ready to be translated for the first time, do the following:
Choosing a translation service provider who uses a tool that supports TMX has several advantages. It is possible to migrate your TM between CAT tools that support the industry standard for TM interchange. This is important not only to free you from dependence on a single translation service provider, but also to allow you to fine-tune your segmentation rules to better match your DITA-based XML source documents you'll be sending for translation. . This section recommends how best to migrate legacy TM to DITA, for use when translating DITA content moving forward. When using a CAT tool that does not support TMX, or supports features that would be lost by using TMX, it is recommended to migrate the legacy TM using the tools provided by the CAT tool. When migrating the TM, keep the following points in mind:
|
DITA Translation Subcommittee Meeting Minutes: 11 September 2006 (Recorded by Gershon Joseph <gershon@tech-tav.com>) The DITA Translation Subcommittee met on Monday, 11 September 2006 at 08:00am PT for 60 minutes. 1. Roll call Present: JoAnn Hackos Gershon Joseph Robert Anderson Bob Doyle (observing) Andrzej Zydron Kevin Farwell Don Day Nancy Harrison Regrets: Special guests from DITA TC: 2. Accept Minutes[1] from 28 August 2006 Accepted. 3. Review open action items --ACTION-- Next draft of the best practice for legacy TM (Gershon Joseph) CONTINUE. [Gershon sent out revised draft for review. Add to next week's agenda] --ACTION-- Nancy Harrison to work on examples of multi-language documents this week and we'll formulate a definition next meeting. CONTINUE. --ACTION-- Andrzej develop a conref best practice document CONTINUE. Andrzej sent updated draft to list. 4. Returning business: 4.1 Once again, review the Best practice for Indexing * approval needed – forward to TC * The current discussions of start and end range implementation should not affect translation. DECISION: Approved Best practice for Indexing document with revisions discussed during the meeting. [Nancy moved, Gershon seconded] -- Meeting adjourned at 09:00am PT -- 4.2 Review Rodolfo’s XLIFF article outline at the Heartsome wiki address http://www.heartsome.org/hswiki/DITA_XLIFF If anyone wants to add sections, comments or any idea, please go ahead and change the wiki. Other continued action items if available. New Business: none ---- [1] http://lists.oasis-open.org/archives/dita-translation/200608/msg0000?.html (minutes not in OASIS mail archive)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]