OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita-translation message

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

Subject: Translation SC Agenda Monday 7 August

We're trying again!

Agenda for Monday 7 August 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 24 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

--ACTION-- Please send review comments to the list of the draft Best Practices for Indexing

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.

    CONTINUE.

    --ACTION-- Everyone to read Rodolfo's XLIFF article[2] and
    provide feedback to Rodolfo this week via the mailing list.

    CONTINUE.

    --ACTION -- Next draft of the best practice for legacy TM (Gershon Joseph)

    CONTINUE.

    --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).

    CONTINUE. (I think this is no longer needed. JTH)

    --ACTION-- Rodolfo and Andrzej to investigate how translation tools can
    differentiate between these keyword elements as inline and standalone
    segments.

    CONTINUE.

    --ACTION-- JoAnn to take to TC our concerns about both the start and end
    index range markers holding the index term.

    COMPLETED.

4) Returning business:

4.1 Review the revision of the draft Best Practices for Indexing (JoAnn)

See the enclosed draft.

New Business:

5.1 Discussion of XLIFF article submitted by Rodolfo Raya. I’ve enclosed a copy of the article with this agenda.

5.2 Handling multi-language documents

Review the three examples provided by Gershon Joseph, Charles Pau, and Tony Jewtushenko ( see attached)

5.3 Andrzej provided examples of the need to change reusable building block to
    the group for discussion.

 5. New Business: (still on hold)

5.1 Handling multi-language documents

Charles Pau and others to provide examples to the list for discussion (multi-language documents best practice)

5.2 Andrjez provided examples of the need to change reusable building block to the group for discussion. (conref best practice)

 

 

JoAnn T. Hackos, PhD
President
Comtech Services, Inc.
710 Kipling Street, Suite 400
Denver CO 80215
303-232-7586
joann.hackos@comtech-serv.com

 

 
--- Begin Message ---
 
 

Best Regards,
Gershon

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

 

From: Tony Jewtushenko [mailto:tony.jewtushenko@productinnovator.com]
Sent: Monday, June 05, 2006 7:07 PM
To: charles_pau@us.ibm.com; gershon@tech-tav.com
Cc: bhertz@sdl.com; 'Bryan Schnabel'; christian.lieske@sap.com; cwong@idiominc.com; dita-translation@lists.oasis-open.org; dpooley@sdl.com; dschell@us.ibm.com; fsasaki@w3.org; 'Howard.Schwartz'; ishida@w3.org; 'Jennifer Linton'; KARA@CA.IBM.COM; mambrose@sdl.com; Peter.Reynolds@lionbridge.com; rfletcher@sdl.com; ysavourel@translate.com
Subject: RE: Examples of multilingual documents

Another example:

 

Boston Edison (electricity provider) sent out warnings about planned work resulting in electrical supply downtime in a variety of languages on the same flyer.  If memory serves me correctly, Spanish, French, Chinese, Russian, and Vietnamese instructions were printed on the same page.

 

Regards,

Tony

 

-----Original Message-----
From: charles_pau@us.ibm.com [mailto:charles_pau@us.ibm.com]
Sent: 05 June 2006 12:19
To: gershon@tech-tav.com
Cc: bhertz@sdl.com; 'Bryan Schnabel'; christian.lieske@sap.com; cwong@idiominc.com; dita-translation@lists.oasis-open.org; dpooley@sdl.com; dschell@us.ibm.com; fsasaki@w3.org; 'Howard.Schwartz'; ishida@w3.org; 'Jennifer Linton'; KARA@CA.IBM.COM; mambrose@sdl.com; Peter.Reynolds@lionbridge.com; rfletcher@sdl.com; tony.jewtushenko@productinnovator.com; ysavourel@translate.com
Subject: Re: Examples of multilingual documents

 


Here are a few more examples:

1.  Government forms (and instructions on filling out forms) and publications in many multilingual countries - Canada, Hong Kong, Singapore, Switzerland, Ireland, Malaysia, India.  Almost all immigration and custom forms (with the US as a major exception).
2.  Magazines in some countries.  Airlines inflight magazines (some have different sections while other have different languages on the same page - to save on reprinting pictures).  I recently flew on Singapore Airlines which has a very extensive on-demand movies, with movies from different countries.  On one page of their magazine they show movies from Hong Kong, Korea, India, France, and Japan, with descriptions in the corresponding language.



Regards,
Charles Pau
Director, Globalization Architecture and Technology
IBM
Tel. +1-617-751-4179   IBM Tie-Line 364-4116
e-mail: charles_pau@us.ibm.com, Notes mail: Charles Pau/Cambridge/IBM@Lotus
URL : http://www.ibm.com/software/globalization
"Tell the rich of the midnight sighing of the poor, lest heedlessness lead them into the path of destruction, and deprive them of the Tree of Wealth." - Bahá’u’lláh


"Gershon L Joseph" <gershon@tech-tav.com>

06/05/2006 03:15 AM

Please respond to
gershon

To

<dita-translation@lists.oasis-open.org>, <cwong@idiominc.com>, <mambrose@sdl.com>, <bhertz@sdl.com>, "'Bryan Schnabel'" <bryan.s.schnabel@tek.com>, <charles_pau@us.ibm.com>, <christian.lieske@sap.com>, <dpooley@sdl.com>, <dschell@us.ibm.com>, <fsasaki@w3.org>, <rfletcher@sdl.com>, "'Howard.Schwartz'" <Howard.Schwartz@trados.com>, "'Jennifer Linton'" <jennifer.linton@comtech-serv.com>, <Peter.Reynolds@lionbridge.com>, <ishida@w3.org>, <tony.jewtushenko@productinnovator.com>, <KARA@CA.IBM.COM>, <ysavourel@translate.com>

cc

 

Subject

Examples of multilingual documents

 

 

 




Following up on action items from last week, here are some multilingual
documents I've come across:

1. A single user manual containing the product's documentation in multiple
languages (in Israel, typically English, Hebrew, Arabic and several European
languages like French, German, Italian, Greek). I've often seen this with
manuals that accompany mobile phones, cameras, and small electronic
equipment. The medical industry also produces a single document (typically
printed on 2 sides of a single sheet of paper) that documents everything
about the medication in every language required by the law of the country
it's sold in. In Israel that includes Hebrew, Arabic, English, Russian, and
a few more I can't think of off-hand. In South Africa it used to be English,
Afrikaans, and several of the local African languages. I think South Africa
now has 11 official languages, so I expect medications to ship with
documentation in all 11 of them. Products sold in Canada probably require by
law documentation in at least French and English (I'm sure someone on the
group will correct me if I'm wrong).

2. A single-language document with a warnings section that contains a set of
warnings in 20 or more languages. For example, the manual would be entirely
in English or French, but the preface or first chapter would contain a
section that lists the same laser (or other) warnings in every language the
field engineer installing the product may speak. Typically, I've seen this
approach in telecommunications equipment (not end-user equipment, but
equipment sold to service providers to integrate into their networks).

If anyone has anything to add to this, or other examples, please discuss on
the list. I doubt we'll get to this item this week (since it's on the bottom
of this week's agenda), but hopefully we'll discuss this next week.

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


--- End Message ---

XML in localisation.doc

DITA Translation Subcommittee Meeting Minutes: 24 July 2006

(Recorded by Gershon Joseph <gershon@tech-tav.com>)

The DITA Translation Subcommittee met on Monday, 24 July 2006 at 08:00am PT
for 60 minutes.

1.  Roll call

    Present:
        Robert Anderson
        Don Day
        Kevin Farwell
        Nancy Harrison
        Gershon Joseph
        Yves Savourel
        Andrzej Zydron

    Regrets:
        JoAnn Hackos

    Special guests from DITA TC:
        France Baril
        Erik Hennum

2.  Accept the minutes[1] of the previous meeting.

    Accepted by acclamation. [Moved by Gershon, seconded by Andrzej.]

3.  Review open action items:

    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.

    CONTINUE.

    --ACTION-- Everyone to read Rodolfo's XLIFF article[2] and
    provide feedback to Rodolfo this week via the mailing list.

    CONTINUE.

    --ACTION -- Next draft of the best practice for legacy TM (Gershon Joseph)

    CONTINUE.

    --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).

    CONTINUE.

    --ACTION-- Rodolfo and Andrzej to investigate how translation tools can 
    differentiate between these keyword elements as inline and standalone 
    segments.

    CONTINUE.

    --ACTION-- JoAnn to take to TC our concerns about both the start and end 
    index range markers holding the index term.

    COMPLETED.

4.  Returning business:

4.1 Open discussion of indexing -- to include France Baril, Erik Hennum, 
    Chris Wong invited to join from the TC. 

    We will use this discussion to clarify the issues the SC has around 
    indexing and to ensure that we all understand how the indexing tags in the 
    prolog and inline are supposed to function from the point of view of 
    translation.

    Erik: Index term is always a subflow. This is not so for keyword: within p 
    it is an inline, but in prolog it's definitely a subflow.

    In places where you don't want to insert the index entry at the start of the 
    containing block element, it should be inserted at the beginning of a sentence
    (in order to keep translation simpler).

    France: Sometimes in one language that has 3 index terms, the translated 
    content should have only 2 index terms. Can DITA accommodate this?
    Andrzej: This is a limitation of XML; one has to map the source document 
    elements 1:1 to the target document.
    This is not part of SC charter, but is good input to W3C ITS
    best practice documents and Yves/Andrzej will discuss it on ITS TC.

4.2 Review the revision of the draft Best Practices for Indexing.

    --ACTION-- Please send review comments to the list.

4.3 Discuss the paper on Rodolfo's web site to be used as a source for an XLIFF 
    best practice document.

    Deferred to future meeting.

5.  New Business: (still on hold)

5.1 Handling multi-language documents

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

    --ACTION-- Gershon to send all input to list

5.2 Andrzej provided examples of the need to change reusable building block to 
    the group for discussion. 

6.0 Announcements

    Andrzej: OSCAR/LISA moved XML-TM draft to public comment. Please review it.
    Andrzej to send links to list.

-- Meeting adjourned at 09:00am PT --

----
[1] http://lists.oasis-open.org/archives/dita-translation/200607/msg00017.html
[2] http://www.heartsome.org/EN/xliff.html

Best Practice for Indexing DITA topics.doc

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