(Recorded by Gershon Joseph <gershon@tech-tav.com>) The DITA Translation Subcommittee met on Monday, 8 May 2006 at 08:00am PT for 60 minutes. 1. Roll call Present: Chris Wong, Patrick Klaassen, Rodolfo Raya, Robert Anderson, Andrzej Zydron, Kevin Farwell, Gershon Joseph, Nancy Harrison Regrets: Don Day 2. Accepted the minutes[1] of the previous meeting. Moved by Andrzej, seconded by Robert, no objections. 3. Reviewed open action items a. Robert to respond to Yves via email and site our decision/recommendation in that email. Robert to write up proposal to be submitted to TC list. Suggestion to make default translate=no on required-cleanup and draft-content.[4,5] CLOSED 4. Discussed Andrzej's note on inline elements: "If we have the opportunity during today's conference call, I would like to discuss the issue of subflows within inline elements. The definition of inline elements for DITA has been a great step forward. We now need to classify which of the inline elements are in fact subflows, that is they do not form part of the linguistic text flow within which they occur. For example footnote text (fn) or index text (indexterm). For localization it is important to be able to separate these out during translation and then to be able to put the text back where appropriate." Reviewed Robert's table[6] of inline elements and noted the following elements that fall into this category: footnote, alt, indexterm, draft-comment, required-cleanup If anyone wants to propose additional elements for this list, plesae post to email list. 5. Discussed Nancy Harrison's outline[3] of Best Practice needs. Discuss next time: How to deal with page range index markers. ACTION: JoAnn to contribute some markup examples. ACTION: Nancy to rephrase adding subflows for translation tools. Meeting adjourned at 09:00am PT. --- [1] http://lists.oasis-open.org/archives/dita-translation/200604/msg00021.html [2] http://lists.oasis-open.org/archives/dita-translation/200605/msg00000.html [3] http://lists.oasis-open.org/archives/dita-translation/200605/msg00002.html [4] http://lists.oasis-open.org/archives/dita-translation/200604/msg00019.html [5] http://lists.oasis-open.org/archives/dita-translation/200604/msg00020.html [6] http://www.oasis-open.org/apps/org/workgroup/dita/download.php/18040/elements.html --- End Message ---
--- Begin Message ---
HI,

As I committed, here is an updated version of my draft best practices summary includin the additios we made to the first vuuletto spur more discussion for our next meeting:

===================== new version ==========================================


Summary of Best Practices discussion on 10Apr2006

We need to present a proposal, for best practices relative to translation, to the main DITA TC.

Best practices fall into various categories:
       for authors                               - base of these are DITA topic-oriented writing guidelines
                                                       - others are more operational
       for implementors                        - setting up stylesheets and specializations to work consistentlyl for translated and multilingual content
       for various toolsvendors           - creating processing that plays well with multilingual content and content to be translated
        for translation tools                -          
Sample Best practice scenarios and requirements
Sample 1. Indexing Guideline Use case and best practices
-        author - inserts index entries immendiately after the start tag of the nearest containing block element, if appropriate, containing the range of text to be indexed; some entries would have a smaller than block-level range
*** need examples of these best practices, especially for <item> and <step> ***
-        output processing - when index entries are encountered, determines the location / scope of the index refernece as the parent element of the index  -        translation tools - when index markers/tags are encountered within an eleent, translation tools shoud generate a subflow - well-configured XLIFF-based tools will do this automatically for you.  We'll need guidelines on suggested configurations.
-        DITA conversion/migration tools - if tool finds an index arker inthe middle of an element, instead of at the beginning of an element, best practice is to move it to the beginning of the nearest containing trandlation segment boundaries.
-       page ranges for incorporation into DITA 1.2

Sample 2  Container items around multilingual bulleted lists
       author - sets xml:lang attribute appropriately for each list item
       processor - produces output appropriate to xml:lang setting for each list item

Sample 3 Sorting multilingual content (in and index, for example)

Sample 4 Generation of translation style sheets (e.g. in English, book titles are often displayed in italic; Japanese has no italic, so book titles are displayed using open/closed corner brackets)
       implementor or vendor issue

Sample 5 Storage of boilerplate text
       Boilerplate text is often kept in one or more .dita files used as a source for conrefs across a document set. How hsould authors / implementors / processors deal with multiple sets of boilerplate files automatically?  DocBook names every file containing generated text with a language entension (two letter only), including English.  A similar scheme, but probably with locale, not just country, would work for DITA documents as well.


Nancy

____
Nancy Harrison
IBM Rational Software
Phone: 781-676-2535
nancyph@us.ibm.com
--- End Message ---

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