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


Help: OASIS Mailing Lists Help | MarkMail Help

xliff-inline message

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

Subject: RE: [xliff-inline] Sample for metadata inline representation

Hi Yves, all,

Good points. Comments below.


-----Original Message-----
From: Yves Savourel [mailto:ysavourel@enlaso.com] 
Sent: Mittwoch, 24. August 2011 08:08
To: xliff-inline@lists.oasis-open.org
Subject: RE: [xliff-inline] Sample for metadata inline representation

Hi all,

One aspect of inline markup we have not discussed yet is bidirectional information.

- It can come from the original source material

- It could be added during the translation process

[CL>>] I think it's important to note that not necessarily translators will be involved.

- Unlike most inline codes (like bold, etc.) which can usually be generic, it may be important for applications using the XLIFF content to see the bidi markers as true bidi markers so they can render the content properly.

[CL>>] I think it is important tob e specific about the bidi marking mechanisms to which we refer. Unicode bidi markers, markup ...

So, for example, if we have this in HTML:

<p>Text with <bdi>Txet thgir-ot-tfel</bdi></p>

Should the <bdi> element be represented as an inline code:

<source>Text with <pc id='1'>Txet thgir-ot-tfel</pc></source>

Or as metadata:

<source>Text with <mrk type='???'>Txet thgir-ot-tfel</mrk></source>

Or both?

[CL>>] Or natively/without XLIFF-specific stuff (e.g. Unicode bidi markers)

Actually this is a general question: If an original code corresponds to a special metadata for which XLIFF has a specific representation how should we encode the original codes?

For example if HTML5 gets a translate attribute, how should we code it? Same for term, etc.

[CL>>] We may get some guidance from http://www.w3.org/TR/its/#associating-its-with-existing-markup

Or should we have provision in the inline codes for a few attributes that would allow us to specify such information in addition to the general inline code information. For example:

<source>Text with <pc id='1' bidi='auto'>Txet thgir-ot-tfel</pc></source>

<source>It would certainly be quite a <pc id='1' translate="no">faux pas</pc></source>

Personally I think having the information along with the inline code for the original data could be better because it allows to keep the two together when moving the markers. 

Any thoughts?

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:

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