OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

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

Subject: FW: Example of use cases for extensions in <source> and <target>

Hi all,

Tha mail below is from Yves.



Hi all,

I'm still not sure how extensions could be handled smoothly in <source> and <target>, but here are a few use cases that may help us thinking about it.

I'm certainly not saying tools could/should deal with those specific cases the way described here, but if we have unrestricted extensions we may see a lot of creative ways of doing things.

1--- Comparison markup

A tool uses XHTML <del> and <ins> elements to markup the result of a comparison between two version of an extracted text item. The entry is not edited as it, but just carried in the XLIFF document for information purpose, and the tool knows how to treat the <ins> and <del> to reconstruct the string to edit when it needs to be translated.

<source xml:lang='en'><htm:ins>The f</htm:ins><htm:del>F</htm:del>ile <ph id='1'>{0}</ph> <htm:ins>was </htm:ins>not found.</source>

2--- Indexed entries

A tool uses a special element to markup indexed entries in a segment. An attribute of that element is used by the tool to let the translator enter the reading order string needed to sort correctly the indexed entry in some language (like Japanese).

<source xml:lang='en'>The <ext:idx readingOrder=''>numeric character references</ext:idx> are used to escape characters un-supported by the output encoding.</source>

3--- Bidi text markers

A tool uses XHTML bidi markers in the target text to mark up a RTL run of text in a LTR sentence. The format of the original text is not HTML, and the markers will be converted by the tool to whatever is appropriate in the original format when merging back the translation (e.g. RTF bidi markers).

<target xml:lang='fr'>Le titre dit "<htm:span dir="rtl">פעילות הבינאום, W3C</htm:span>" en hébreu.</</target>

4--- Markup for editor

A tool uses its own elements to indicate different possible translations provided by the translator. The entry will be then edited and a final translation chosen.

<target xml:lang='en-gb'>It may seem petty to <ext:options><ext:opt id='1'>cavil</ext:opt><opt id='2'>raise frivolous objections</ext:opt></ext:options> at minor flaws given the film's unquestionable excellence as a whole, but the ending did seem to lack credibility.</target>

5--- Inserting new formatting

A tool uses XHTML character formatting elements to introduce new formatting in the translation. The merging tool will know how to convert such elements to the appropriate codes in the original format.

<target xml:lang='fr'>Nos invités peuvent assouvir leur esprit d'aventure et leur <htm:i>wanderlust</htm:i> en découvrant les differentes iles de notre petit archipel.</target>


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