RE: [xliff-inline] Teleconference - Aug-10-2010 - 13:30 UTC - Minutes

[Yves Savourel <ysavourel@translate.com>]

XLIFF Inline Markup Subcommittee Teleconference - Minutes
Aug-10-2010

=== 1) Admin

Present: Asgeir, Arle, Yves, Dimitra,
Regrets: Lucia

Minutes of previous meeting:
http://lists.oasis-open.org/archives/xliff-inline/201007/msg00004.html

Arle moves to accept the minutes.
Asgeir seconds.
None opposed.


=== 2) Discussion: Requirements

Requirement working page:
http://wiki.oasis-open.org/xliff/OneContentModel/Requirements

We had several action items:

-- ACTION ITEM: Yves to find a real example for requirement #4
--> Not done yet, still pending.

-- ACTION ITEM: Arle to bring any additional requirement from OSCAR.
--> pending.


Requirement #8:
http://lists.oasis-open.org/archives/xliff-inline/201007/msg00005.html

The wording adopted after discussion is:

[
Must be able to identify uniquely an inline code within a segment (<source> and/or <target> in XLIFF 1.2 or <seg> in TMX)

An inline code may be associated with external metadata. In order to link the code and its associated metadata, a way to identify the inline code uniquely within the segment is needed.
]


Requirement #9:
http://lists.oasis-open.org/archives/xliff-inline/201008/msg00001.html

The wording adopted after discussion is:

[
Must be able to associate the same codes between the source and the target segments.

For example, in the following source and translation:

English: "The text is in <b>bold</b> and <i>italics</i>."
Yoda-English: "In <i>italics</i> and <b>bold</b> the text is."

The tags <b> </b>, <i>, and </i> of the source should be mappable to the ones in the translation.
]


After discussion, two new requirements were added: duplicating codes and adding codes.

#10

[
Must be able to represent the duplication of inline codes in the segment

Sometimes the translation of a formatted text requires the translation to split the source into several parts
in different places in the segment and the original codes need to be replicated.

He often <B>came a cropper </B> due to stress.
Er is oft <B>auf die Nase</B> wegen Stress <B>gefallen</B>.
]

#11

[
Must be able to represent inline codes added to the segment

Translated text may need to have extra information inserted in the form of inline codes.
For example directionality markers for bidirectional languages.

TODO: example

Another example: The following Japanese text has a title between special marks that are rendered as italics in English:

JP: 私は『時間コレラの』愛を読む
EN: I just read <i>Love in the Time of Cholera</i>
]


Requirement #12: (was #10, #11, and #12)

After discussion, the three requirements related to the representation of the native data were grouped into a single one (#12), with the following wording:

[
There must be three ways to deal with the native data corresponding to an XLIFF inline code:

a) not to store it at all

b) to store it along with its XLIFF representation

c) to store a pointer to it along with its XLIFF representation
]


Next meeting Sep-14-2010
-end-