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: Agenda Translation Subcommittee -- Monday 28 August 2006

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

    CONTINUE.

 --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-- Nancy Harrison to work on examples of multi-language documents this week and we'll formulate a  definition next meeting.

    CONTINUE.

--ACTION-- Andrzej develop a conref best practice document

    CONTINUE.

4) Returning business:

4.1  Final review the Best practice for Indexing (attached) – approval needed – forward to TC

       The current discussions of start and end range implementation should not affect translation.

4.2  Handling multi-language documents (see attached examples)

       Develop a definition of multi-language documents.

4.3 Discussion of Bryan Schnabel's feedback email on the XLIFF tools for DITA

    Rodolfo tested and it works OK. Requires further testing with keyword/index decisions at today's meeting. XSL cannot do     segmentation.

4.4 Review Andrzej’s draft statement on CONREF best practices (see attached)

4.5 Refer to Rodolfo’s XLIFF article outline at the Heartsome wiki address

http://www.heartsome.org/hswiki/DITA_XLIFF

If anyone wants to add sections, comments or any idea, please go ahead and change the wiki.

New Business:

none

 

 

 

JoAnn T. Hackos, PhD

President

Comtech Services, Inc.

710 Kipling Street, Suite 400

Denver, CO 80215

303-232-7586

joann.hackos@comtech-serv.com

www.comtech-serv.com

 

DITA Translation Subcommittee Meeting Minutes: 21 August 2006

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

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

1.  Roll call

    Present:
        Don Day (acting as chair)
        Gershon Joseph
        Kevin Farwell
        Rodolfo Raya
        Robert Anderson
        Andrzej Zydron
        Nancy Harrison

    Regrets:
        JoAnn Hackos

    Special guests from DITA TC:

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

    Accepted.

3.  Review open action items:

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

    CONTINUE.

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

    CLOSED.
    [Keyword in prolog is always standalone; keyword anywhere else is inline.
    This is already noted in Robert's list of translatable elements.]

4.  Returning business: 

4.1 Handling multi-language documents

    Please formally define a multi-language document

    See examples submitted by Gershon Joseph, Charles Pau, and Tony 
    Jewtushenko.

    --ACTION-- Nancy to work on examples this week and we'll formulate a 
    definition next meeting.

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

    Revisit this next week assuming the TC resolves the index range open issues.

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

5.  New Business:

5.1 Discussion of Bryan Schnabel's feedback email on the XLIFF tools for DITA

    Rodolfo tested and it works OK. Requires further testing with keyword/index
    decisions at today's meeting. XSL cannot to segmentation.

5.2 Discussion of Rodolfo's draft of the article on XLIFF
    
    --ACTION-- Rodolfo to work on the draft XLIFF article. Updates will be 
    posted to Rodolfo's Wiki (URL will be provided).

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

    Some of the issues that apply to conref are discussed in the article
    Towards an internationalized and localized TEI[2]:
    
    --ACTION-- Andrzej working on conref best practice document.

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

----
[1] http://lists.oasis-open.org/archives/dita-translation/200608/msg00007.html
[2] http://tei.oucs.ox.ac.uk/Oxford/2006-05-17-kyoto/i18n-slides.xml

Best Practice for Indexing DITA topics.doc

--- 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 ---
--- Begin Message ---
Title: [dita-translation] CONREF best practices

Hi Everyone,

As regards XML best practices in general please refer to my paper from
XML 2004 USA which details many of the do's and dont's regarding XML
localization:

http://www.idealliance.org/proceedings/xml04/papers/49/paper.html

As regards best practices concerning the use of the DITA conref element
I would like to propose the following:

Great care should be taken regarding the use of the 'conref' element.
Although the conref element may appear as a very efficient artifice to
allow for the simple substitution of product names etc. allowing for the
runtime resolution of given parameters this can cause grammatical
problems with highly inflected and gender sensitive languages such as
most Slavonic and Germanic languages.

What works extremely well for English or French source text can result
in ungrammatical text for given target languages. Such an outcome is
generally undesirable as it will reflect badly on the documentation
concerned.

As a general rule the safest way to use conref is for the inclusion of
grammatically complete sentences or phrases (those that can stand alone
and do not rely on the surrounding context).

Never use conref to substitute common nouns or noun phrases such as for
example 'hammer' or 'screw driver' etc.

Where the conref is used for proper nouns, such as 'Ford Focus' the the
safest solution is to insure that the proper noun is always the main
subject of the sentence, e.g.:

Do not use:

Driving the Ford Focus is an exhilarating experience.


Rather use:

The Ford Focus provides an exhilarating diving experience.

The subject of a sentence is in the nominative case and therefore does
not normally require inflection.

The translators should also receive appropriate instructions to insure
that the substituted proper noun is translated as the subject of the
sentence.


Best Regards,

AZ

--


email - azydron@xml-intl.com
smail - c/o Mr. A.Zydron
        PO Box 2167
         Gerrards Cross
         Bucks SL9 8XF
        United Kingdom
Mobile +(44) 7966 477 181
FAX    +(44) 1753 480 465
www - http://www.xml-intl.com

This message contains confidential information and is intended only
for the individual named.  If you are not the named addressee you
may not disseminate, distribute or copy this e-mail.  Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses.  The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission.  If
verification is required please request a hard-copy version. Unless
explicitly stated otherwise this message is provided for informational
purposes only and should not be construed as a solicitation or offer.





--- End Message ---

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