NOTE: This wiki is provided by the OASIS standards consortium as a collaborative tool for the OASIS DITA Learning and Training Content Specialization Subcommittee. Members of the Subcommittee are permitted to post to these pages (SC Members Page). As this is an official workspace of the TC, the OASIS IPR Policy and other OASIS rules apply to its use.
To learn more about the work of the Subcommittee, send a comment, or join this effort, visit the OASIS DITA Translation Subcommittee homepage. Prospective members of the subcommittee must first join the OASIS DITA Technical Committee (TC Members Page).
Wiki pages are transient documents, so intermediate edits may not be saved. SC members should move all permanent work and stable artifacts to the SC's document repository, where the archival work product of the SC also can be viewed by the public.
Wiki home page for the OASIS DITA Translation Subcommittee
Welcome! The URL for this page is: http://wiki.oasis-open.org/dita/TranslationSubcommittee
Agenda for 12August 2011
8:00-8:05 am Roll call PDT
1) Roll Call
2) New Action Items
- 2.1. Now that xml:lang has been added to the "dita" tag in DITA 1.2, we should consider if dir and/or translate should also be added. (I don't think translate should, but I wonder about dir.) 2.2 Glossary sort-as proposal
I'm cc'ing the DITA Translation SC, as this feature is mostly intended to facilitate translation.
I think we could use more examples of what this feature would be used for, i.e. What things are sorted alphabetically in output, and in what types of publications? It's plausible to me that reference topics and definition list items should be sorted alphabetically in some publications, but I don't know what these publications are. The proposal template has the following questions, which I can easily answer for glossary entries but not for anything else:
- Who will benefit from this feature? - What is the expected benefit? - How many people probably will make use of this feature? For example, everyone, many, or few. - How much of a positive impact is expected for the users who will make use of the feature?
Add a <glossary-sort-as> element to facilitate sorting glossary entries by something other than the <glossterm> element. Email: http://lists.oasis-open.org/archives/dita/200903/msg00060.html JoAnn requests that the translation SC should review / provide input to the proposal Eliot suggests a more general sort mechanism would be better (not exclusively glossary). Added Eliot as an additional owner.
3.1 ACTION: Need to publish the multi-language document.
Gershon to investigate whether he can use a client's samples.
Gershon will assemble all the examples into the template for the TC; need to add the examples to the Multilanguage Best Practice. CONTINUED. Awaiting legal OK; Gershon is selecting items for use in the Best Practice. Decision to submit the BP to the TC for review without these items and we'll update them after Gershon gets approval from his client, since it's going to take a while.
See the attached summary document.
4.3 Discussion of the translate attribute and “partial” translations
Note from Steve Anderson to the yahoo DITA list:
“Many elements in DITA include a translate attribute. It has a value of yes or no. We've been using it in a way similar to the filterable attributes (platform, audience, otherprops, etc.). Before sending our files out for translation, we remove all the content that is marked as translate="no".
As an aside, I'm surprised that the translate attribute isn't filterable like audience. Anyway, translate yes/no is good for simple situations, but for more complex situations it fails. For example, if you have a topic that is translated into some, but not all languages (a "partial" translation), you can't set translate="no" on it, since, in some cases, it should be translated.”
Note from Felix Sasaki you could use a mechanism like ITS "Localization Note" for this. See the definition at http://www.w3.org/TR/its/#locNote-datacat and some BP about it at http://www.w3.org/TR/xml-i18n-bp/#DevLocNote http://www.w3.org/TR/xml-i18n-bp/#AuthLocNote in your case having an attribute "locNote" which qualifies what kind of "partial" translation is needed could solve the problem.
Note that I'm not necessarily proposing to use ITS "Localization Note" natively, but I'm only pointing you to a potential approach to solve the issue.
4.5 Discussion of information The Internationalization Tag Set (ITS) Working Group has published a Group Note of Best Practices for XML Internationalization. This document provides a set of guidelines for developing XML documents and schemas that are internationalized properly. Following the best practices describes here allow both the developer of XML applications, as well as the author of XML content to create material in different languages.
Section 5 of the document "ITS Applied to Existing Formats" http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/#Modularization contains a section about ITS and DITA http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/#dita
Thanks a lot to the people on this list who gave feedback on drafts on this section, and this document in general.
5) New business:
Do we continue this subcommittee after we complete the three remaining best practices documents: acronyms, glossary, multi-language?
9:00 am Adjourn
The formal name of the subcommittee is "The OASIS DITA Translation Subcommittee".
The OASIS DITA Translation Subcommittee has the following goals:
1) Develop an effective liaison with the OASIS XLIFF technical committee and the W3C ITS working group so that the DITA TC can work together with those interested providing for the needs of the information-development community from authoring through localization to the production of final deliverables in multiple languages.
2) Establish guidelines that promote best practices for authoring, workflow, and tools that allows information to move seamlessly from original authors and editors through translators and production specialists handling the intricacies of multiple languages and cultures.
3) Add to the various specifications methods that will help vendors and service providers comply with DITA and translation-oriented standards.
4) Add a DITA to XLIFF to DITA tool set to the DITA Open Source Toolkit so that content can move seamlessly along the full information development life cycle.
Requirements for the use of acronyms
The acronym proposal is intended to meet the requirements listed in this page (to be moved here once they are final): AcronymRequirements
Notes about Acronyms:
- Some acronyms are never translated, especially those that are intended for a knowledgeable, technical audience.
- Some acronyms represent a brand name for which the original expanded form is no longer used or is secondary to the acronym.
- Acronyms such as xml, jpg, html, and so on are typically used in their original form.
- Acronyms that have equivalent expressions in other languages are typically translated. United Nations (UN) and Weapons of Mass Destruction (WMD) have equivalents in other languages besides English.
- Some acronyms are translated for clarity and also referred to in their original untranslated form. OASIS will be translated so that readers understand its significance in their native languages but the original acronym will be retained in the translation. The acronym is used, for example, to locate the organization in an electronic search.
In printed text or PDFs, the first instance of a term is expanded, followed by its acronym in parentheses or other equivalent form. United Nations (UN) is thus presented in English. In subsequent instances, the acronym is used instead of the expanded form.
In online text, the acronym may occur in all instances, given that a "first instance" may be difficult to define. The expanded form may be presented as a pop-up or mouse-over in all cases.
Home pages for the OASIS DITA TC and this subcommittee
Member pages for the OASIS DITA TC and this subcommittee
Wiki home page for the OASIS DITA TC