RE: Example indexterm

["Chris Wong" <cwong@idiominc.com>]

Sorry I couldn't make this meeting. I was called away to an urgent problem. 

Isn't this more a tools/adaptation issue than an XML issue? The limitation is in the translation tools that do not permit elimination of tags. DITA can certainly express the indexterm translation you want, but the tool won't let you. Can you change attributes in the tags during translation? Conditional processing might do the trick. Your example:

<indexterm>accueil
	<indexterm>page d'</indexterm>
</indexterm>

This can be translated as:

<indexterm>homepage<indexterm audience="nobody"></indexterm></indexterm>

During processing, your DITAVAL can simply state that content intended for audience="nobody" should be eliminated. This can handle cases where elements are eliminated in translation, but not where elements are added. On the other hand, it does not sound like you want to add new elements in translation.

Chris
 

-----Original Message-----
From: France Baril [mailto:France.Baril@ixiasoft.com] 
Sent: Monday, July 24, 2006 11:38 AM
To: JoAnn Hackos; dita-translation@lists.oasis-open.org; Chris Wong; mambrose@sdl.com; bhertz@sdl.com; Bryan Schnabel; charles_pau@us.ibm.com; christian.lieske@sap.com; dpooley@sdl.com; dschell@us.ibm.com; esrig@lucent.com; fsasaki@w3.org; rfletcher@sdl.com; Howard.Schwartz; Jennifer Linton; ishida@w3.org; tony.jewtushenko@productinnovator.com; KARA@CA.IBM.COM; ysavourel@translate.com
Cc: Erik Hennum; Chris Wong
Subject: Example indexterm

Can I suggest that we add to the agenda the question about not translating indexterms and keywords in an exact one to one match. It should be possible to add or remove indexterms and keywords. This, to my knowledge, cannot be managed by any tool. 

For example, in Qc we have these indexterm for info about email.

<indexterm>courriel</indexterm>
<indexterm>mél</indexterm>
<indexterm>email</indexterm>

That's because mél is used in France, courriel in Québec and many users use the English term email. It does not make sense to have 3 entries in English, one would be enough. You meet the same issue when a two word expression in one language becomes a one work expression.

<indexterm>accueil
	<indexterm>page d'</indexterm>
</indexterm>

<indexterm>homepage</indexterm>

This example is so so because there are work arounds, but it's the only one I could think of at this time.  

-----Original Message-----
From: JoAnn Hackos [mailto:joann.hackos@comtech-serv.com]
Sent: July 23, 2006 8:09 PM
To: dita-translation@lists.oasis-open.org; cwong@idiominc.com; mambrose@sdl.com; bhertz@sdl.com; Bryan Schnabel; charles_pau@us.ibm.com; christian.lieske@sap.com; dpooley@sdl.com; dschell@us.ibm.com; esrig@lucent.com; fsasaki@w3.org; rfletcher@sdl.com; Howard.Schwartz; Jennifer Linton; ishida@w3.org; tony.jewtushenko@productinnovator.com; KARA@CA.IBM.COM; ysavourel@translate.com
Cc: France Baril; Erik Hennum; Chris Wong
Subject: OASIS DITA Translation Subcommittee -- Agenda 24 July 2006

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

Unfortunately, I will be traveling at the meeting time on Monday. Don Day has gratiously agreed to chair the meeting. JoAnn

Roll Call

Accept Minutes from 17 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-- 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.
  In Progress
  --ACTION-- Everyone to read Rodolfo's XLIFF article[2] and
    provide feedback to Rodolfo this week via the mailing list.
http://www.heartsome.org/EN/localisation.html
  In Progress

 

--ACTION -- Next draft of the best practice for legacy TM In progress Gershon Joseph

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

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

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

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

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

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




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
joannhackos Skype
www.comtech-serv.com