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: DITA Translation Subcommittee -- Agenda 21 August 2006

Agenda for Monday 21 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

JoAnn -- Sorry to miss today's meeting -- teaching the DITA Boot Camp -- Don Day will chair

Roll Call

Accept Minutes from 14 August 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.

    completed.

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

    completed.

       -- ACTION -- Next draft of the best practice on indexing (JoAnn Hackos to complete when the TC reaches             a decision on start and end range)

    CONTINUE.

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

    CONTINUE. 

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

    CONTINUE.

4) Returning business:

4.1  Handling multi-language documents

Please formally define a multi-language document

See examples Gershon Joseph, Charles Pau, and Tony Jewtushenko ( see attached).

4.2  See the Best practice for Indexing (attached) -- no changes since last meeting

4.3 No other (unless Gershon has an update of the best practice on TM

New Business:

5.1 Discussion of Bryan Schnabel's feedback email on the XLIFF tools for DITA (email is enclosed)

5.2 Discussion of Rodolfo's draft of the article on XLIFF

5.3 Initial discussion of the best practice on conref (Andrjez) -- reusable building blocks 

 

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

 

 

Best Practice for Indexing DITA topics.doc

DITA Translation Subcommittee Meeting Minutes: 14 August 2006

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

The DITA Translation Subcommittee met on Monday, 14 August 2006 at 08:00am PT
for 40 minutes.

1.  Roll call

    Present:
        Robert Anderson
        Don Day
        Kevin Farwell
        JoAnn Hackos
        Nancy Harrison
        Gershon Joseph
        Rodolfo Raya
        Yves Savourel

    Regrets:
        Andrzej Zydron

    Special guests from DITA TC:

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

    Accepted.

3.  Review open action items:

    --ACTION-- Rodolfo to test some samples with Brian Schnabel's tool.

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

    COMPLETED. Outline approved.

    --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-- Rodolfo and Andrzej to investigate how translation tools can 
    differentiate between these keyword elements as inline and standalone 
    segments.

    COMPLETED. (JoAnn to discuss bad keyword example with David Walters)

4.  Returning business:

4.1 Review the revision of the draft Best Practices for Indexing.
    We cannot complete this item until the indexing group comes up with a 
    decision on handling index range tags. See the changes marked in the 
    current draft attached here.

    Discussed those parts that do not deal with index ranges.

    As soon as index range is frozen JoAnn will update the document.

5.  New Business:

5.1 Discussion of Bryan Schnabel's feedback on the XLIFF article submitted by 
    Rodolfo Raya. I’ve enclosed a copy of the article and Bryan's email.

5.2 Handling multi-language documents

    Review the three examples provided by Gershon Joseph, Charles Pau, and 
    Tony Jewtushenko

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

6.  Announcements


-- Meeting adjourned at 08:40am PT --

----
[1] http://lists.oasis-open.org/archives/dita-translation/200607/msg000xx.html
[2] http://www.heartsome.org/EN/xliff.html
--- Begin Message ---
Title: RE: DITA Translation Subcommittee Meeting Minutes: 14 August 2006

Hi Rodolfo,

In reading the most recent meeting minutes, I noticed that you've taken
an action item to run some test files through my xliffRoundTrip Tool.

> 3.  Review open action items:
>
>    --ACTION-- Rodolfo to test some samples with Brian Schnabel's tool.

Are these tests to be done with my generic tool
(http://sourceforge.net/projects/xliffroundtrip/), or are you going to
do them with the prototype tool (DITA-XLIFF_round_trip) I optimized to
perform better with DITA files?

I attached a zip file of the latter, along with powerpoint slides that
distinguish between the two tools, and shows how to use the prototype
DITA-XLIFF tool.

I think the DITA-XLIFF tool could be a better fit, maybe, maybe not.
Although this prototype only works as a simple command-line, bat file,
whereas the other has the Java User Interface, and so on. I've been
trying to carve out a little time to work on both of these tools.

I'm not sure what the purpose of your test is.  But if you conclude that
the prototype DITA-XLIFF tool shows promise, I'd be willing to further
develop it toward serving the DITA community (license it in a way
consistent with the DITA TC's goals, wrap it in a friendly User
Interface, create some user documentation, etc.). 

If I'm barking up the wrong tree, feel free to say so.

Good luck; let me know if I can be of any help.

Bryan Schnabel
(. . . I guess I should try to attend some of these meetings rather than
responding to meeting minutes)

-----Original Message-----
From: Gershon L Joseph [mailto:gershon@tech-tav.com]
Sent: Monday, August 14, 2006 8:47 AM
To: dita-translation@lists.oasis-open.org; mambrose@sdl.com;
pcarey@lexmark.com; rfletcher@sdl.com; bhertz@sdl.com; ishida@w3.org;
tony.jewtushenko@productinnovator.com; christian.lieske@sap.com;
'Jennifer Linton'; 'Munshi, Sukumar'; charles_pau@us.ibm.com;
dpooley@sdl.com; fsasaki@w3.org; ysavourel@translate.com;
dschell@us.ibm.com; 'Bryan Schnabel'; 'Howard.Schwartz'; KARA@CA.IBM.COM
Subject: DITA Translation Subcommittee Meeting Minutes: 14 August 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

steps.ppt

DITA-XLIFF_round_trip.zip

--- End Message ---
--- 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 ---

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