Re: [xliff-inline] Requirements - #9

[Arle Lommel <arle@lisa.org>]

Yves, I don’t know if we want to complicate this with what is something of an edge case, but what about a situation like one in which you have different codes in the source and target that should be associated? For example, I have something like this (using HTML-like tags):

English: This is some <b>bold text</b>
Japanese: これは、いくつかの<dotAccent>太字のテキスト</dotaccent>です

Pardon my Google Translate version of Japanese.

Also, how would we handle a case where one set of tags in one language could correspond to two (or more) in another? (For example, a syntactic unit is bolded in English, but it corresponds to two syntactic units that are separated in a target language and that both should appear as bold with Roman text between them?

So the requirement seems simple enough in the abstract, but how do we describe the messy realities and how far do we need to go to support them?

-Arle

On 8/4/10 11:42 AM, sic scripsit Yves Savourel:

002001cb33eb$b21cbcb0$16563610$@com" type="cite">

Hi all,

The discussion on requirement #8 is in this thread, still opened for discussion:
http://lists.oasis-open.org/archives/xliff-inline/201007/msg00007.html


I'll take the silence for a tentative consensus and move on to #9:

#9: Currently we have:
http://wiki.oasis-open.org/xliff/OneContentModel/Requirements

[
Should 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 codes <b> </b>, <i>, and </i> of the source should be mappable to the one in the translation
]


I would propose the following tweaks:

"Must allow to associate the same codes between the source and the target segments"

And:

"The codes <b> </b>, <i>, and </i> of the source should be mapped to their corresponding codes in the translation"


Cheers,
-ys



---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php