[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: DITA Translation Subcommittee Meeting Minutes: 15 May 2006
Best Regards, Gershon --- Gershon L Joseph Member, OASIS DITA and DocBook Technical Committees Director of Technology and Single Sourcing Tech-Tav Documentation Ltd. office: +972-8-974-1569 mobile: +972-57-314-1170 http://www.tech-tav.com
DITA Translation Subcommittee Meeting Minutes: 15 May 2006 (Recorded by Gershon Joseph <gershon@tech-tav.com>) The DITA Translation Subcommittee met on Monday, 15 May 2006 at 08:00am PT for 60 minutes. 1. Roll call Present: Don Day, Gershon Joseph, Kara Warburton, Kevin Farwell, Robert Anderson, David Walters, Nancy Harrison Regrets: JoAnn Hackos, Andrzej Zydron, Rodolfo Raya 2. Accepted the minutes[1] of the previous meeting. Moved by Gershon, seconded by Don, no objections. 3. Old Business: a. Review Nancy's revision of the indexing best practice enclosed. 4. New Business: a. Discuss the second item on handling inline elements properly (alt text, footnote, draft comment, required element). Please pay particular attention to defining how the authors should handle this. DONE. b. If possible, continue with the next best practice in Nancy's list. Don: Index entries are for in-situ index entries; <keyword> should be used for index terms that apply to the entire topic. "If appropriate, the index entry should contain the range of text to be indexed" - This refers to page ranges. The index term is defined inside the index marker. Start range should be at beginning of start block (i.e., parent block element); end range markup should be at end of end block element. - Tools should implement range from start of start element containing the start index marker to end of end element that contains the end index marker, regardeless of the location of the start and end markers. ACTION (from previous meeting) JoAnn to provide example markup "The author should insert -- where ???" - Put them where it's logical in the source document. "When these elements are encountered, the tool should interpret the location of the container element for the inline element as the parent element of the element. ???" - We don't have anything to say here, remove this sentence. "Well-configured XLIFF-based tools do this automatically" Change to: In generaral, XLIFF-based translation tools can be configured to do this automatically. Agenda item for next week: What other best practices do we need to discuss? e.g. maximize usage of conref (reusable blocks)... Meeting adjourned at 09:00am PT. --- [1] http://lists.oasis-open.org/archives/dita-translation/200605/msg00006.html
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]