RE: [dita-translation] DITA SC Agenda Monday 12 2006

Best Regards,
Gershon

---
Gershon L Joseph
Member, OASIS DITA and DocBook Technical Committees
Director of Technology and Single Sourcing
Tech-Tav Documentation Ltd.

Agenda for Monday 12 June 2006

Note: Please be certain to review the ITS documents from Yves Savourel before the meeting tomorrow.

I11:00 am - 12:00 am Eastern Standard Team (-5 GMT)

DITA Technical Committtee teleconference

USA Toll Free Number: 866-566-4838

USA Toll Number: +1-210-280-1707

PASSCODE: 185771

Roll Call

Approve Minutes from 6 June 2006 (enclosed for those who are not TC

members)

http://www.oasis-open.org/apps/org/workgroup/dita-translation/

<http://www.oasis-open.org/apps/org/workgroup/dita-translation/>

Returning Business:

1) Discussion item from Yves Savourel

As you may know, the W3C has recently published the Last Call Working Draft for ITS (See [1]) as well as the First Working Draft of a companion document: "Best Practices for XML Internationalization" (See [2]).

[1] <http://www.w3.org/TR/2006/WD-its-20060518/>

[2] <http://www.w3.org/TR/2006/WD-xml-i18n-bp-20060518/>

The second document include examples of how to use ITS with a few specific document types (See the "ITS Applied to Existing Formats"

section). In the next draft we would like to include DITA in that list.

The attached file is a try for the possible default rules to process DITA with ITS. We would appreciate very much if some of you had the time to review it and make sure we have not made any mistake, or forgot anything. For example, I'm not sure if the dir attribute should be there or not. I'm also not sure if we have all subflow elements listed. Maybe we need two rule sets: on for the current version of DITA and one for the upcoming one (although if there is no conflict and a single rule set could be used that would be better).

The specification document [1] should help you understand each element in these rules. The Last Call review for the specification ends on June-30. The Best Practices document will still go through several drafts.

2) Discuss Gershon Joseph's draft of the best practice for legacy TM

Attached to this email for non-TC members.

3) Management of conref blocks for translations

Standarized (boilerplate) text is often kept in one or more .dita files used as a source for conrefs across a document set.

All boilerplate content for a language must be stand-alone.
Boilerplate text must be stand-alone phrases to avoid problems translating
it into some languages, where it does not fit into the surrounding text.

Depending on the conref target, the conref target should be
translated before the parent document that refers to the conref
is translated.

Conreffing to an inline element may result
            in a badly translated phrase with respect to its surrounding content,
            so we should probably be against this. Examples: singular/plural,
            prepositions, acronyms e.g. ABS (antilock breaking system) so if
            you conref to the text itself, the translated text may not read
            correctly.

Action Item: Andrjez will provide examples to the group for discussion.

4) XLIFF transforms

Discuss plans for Rodolfo's tests of their XLIFF transforms and possible release to open source. Ask if there is a proposed date.

Andrzej and Rodolfo have successfully converted DITA to XLIFF and back.
Rodolfo plans to publish their converter as open source.

New Business:

4) Handling multi-language documents

Charles Pau and others to provide examples to the list for discussion

dita-translation message