[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: DITA Translation Subcommittee Agenda for 17 July 2006
Agenda for Monday 17 July 2006
11:00 am - 12:00 am Eastern Standard Team DITA Technical Committee teleconference USA Toll Free Number: 866-566-4838 USA Toll Number: +1-210-280-1707
PASSCODE: 185771
Roll Call
Accept Minutes from 10 July 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
4) Returning business:
4.1 Discuss submission of the xml:lang and the dir recommendations as Commitee Drafts to the TC.
A Committee Draft is an OASIS deliverable so the publishing requirements are the same :-) Basically the output should resemble the OASIS templates - if we need to create the cover information separately and then prepend to both the HTML and PDF I don't see a problem with that, although having all the content in a single clump is optimum. (from Mary MacRae)
4.2 Discuss Gershon Joseph's next draft of the best practice for legacy TM
4.3 Discuss the paper on Rodolfo's website to be used as a source for best practice document.
4.4 Review the revision of the draft Best Practices for Indexing.
//JoAnn's 2nd draft. not yet complete. Please add comments to the draft.
5. New Business:5.1 Handling multi-language documents
Charles Pau and others to provide examples to the list for discussion
5.2 Andrjez provided examples of the need to change reusable building block to the group for discussion.
ACTION -- Rodolfo to prepare an outline for this best practice document for translating DITA and submit to list for discussion at a future meeting.
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.
If you keep the following points in mind, you should be able to maximize your existing translation memory when you send your DITA documents for translation:
When your DITA content is ready to be translated for the first time, do the following:
Once the translator has completed the translation, the TM should be exported as a TMX file. This TMX will now correctly tag the DITA block elements as well as correctly segment the sentences, and should therefore be used as the TM for the next DITA-based translation project. For future localization projects, the new TMX should yield exact matching at the segmentation level used for translation (block or sentence).
|
DITA Translation Subcommittee Meeting Minutes: 10 July 2006 (Recorded by Gershon Joseph <gershon@tech-tav.com>) The DITA Translation Subcommittee met on Monday, 10 July 2006 at 08:00am PT for 70 minutes. 1. Roll call Present: Robert Anderson Don Day Kevin Farwell JoAnn Hackos Gershon Joseph Charles Pau Rodolfo Raya Yves Savourel David Walters Regrets: Felix Sasaki Andrzej Zydron 2. Accept the minutes[1] of the previous meeting. Accepted. [Moved by Don, seconded by Yves, no objections.] 3. Review open action items: ACTION -- Don to inform us where to publish our best practices. Closed. See summary[3]. ACTION -- Rodolfo to prepare an outline for this best practice document for translating DITA and submit to list for discussion at a future meeting. At that meeting, SC should agree on the outline. In progress. 4. Returning business: 4.1 Discuss Gershon Joseph's next draft of the best practice for legacy TM In progress. Gershon hopes to submit draft tomorrow for review. 4.2 X-LIFF transforms continued discussion. Discuss Rodolfo's draft outline for an XLIFF best practice document for translating DITA if it is ready to discuss. --ACTION-- Everyone to read Rodolfo's XLIFF article[2] and provide feedback to Rodolfo this week via the mailing list. 4.3 Discuss JoAnn's draft Best Practices for Indexing. Want to clarify this document. It will be incorporated into the full Best Practice statement that JoAnn and Andrzej are authoring. --ACTION-- Robert and JoAnn to work on wording of note to keyword element noting that it is considered inline when inside topics, but as standalone segments when inside <keywords> (in prolog). --ACTION-- Rodolfo and Andrzej to investigate how translation tools can differentiate between these keyword elements as inline and standalone segments. --ACTION-- JoAnn to take to TC our concerns about both the start and end index range markers holding the index term. -- Meeting adjourned at 09:10am PT -- 5. New Business: 5.1 Handling multi-language documents Charles Pau and others to provide examples to the list for discussion Don requests to move this item to the agenda of the next meeting. 5.2 Andrzej provided examples of the need to change reusable building block to the group for discussion. --- [1] http://lists.oasis-open.org/archives/dita-translation/200606/msg00018.html [2] http://www.heartsome.org/EN/xliff.html [3] http://lists.oasis-open.org/archives/dita-translation/200607/msg00008.html
Best Practice for Indexing DITA topics.doc
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]