Re: [xliff-comment] XLIFF 2.1 csprd01: Translate Annotation and inline elements

Thanks, Jano,

feel free to propose a rendering module in an XLIFF Symposium or through this mailing list.

Anyways, we will not consider rendering rules or guidance for XLIFF Version 2.1

Cheers and thanks for the valuable input you provided in response to XLIFF 2.1 1st Public Review

dF

Dr. David Filip
===========

OASIS XLIFF OMOS TC Chair

OASIS XLIFF TC Secretary, Editor, Liaison Officer

Spokes Research Fellow

ADAPT Centre

KDEG, Trinity College Dublin

Mobile: +420-777-218-122

On Thu, Feb 2, 2017 at 3:59 PM, Ján Husarčík <> wrote:

Hello David,

I would like to retract https://issues.oasis-open.org/browse/XLIFF-16, as does not address the whole problem.

Maybe this and other rendering rules/requirements could be considered as a module for next version.

Thanks,
Jan

On Mon, Nov 21, 2016 at 7:56 PM, David Filip <> wrote:

Thanks, Jano,

please follow the disposition here:

https://issues.oasis-open.org/browse/XLIFF-16

Any comments please post in this thread

Cheers and thanks

dF

Dr. David Filip
===========

OASIS XLIFF OMOS TC Chair

OASIS XLIFF TC Secretary, Editor, Liaison Officer

Spokes Research Fellow

ADAPT Centre

KDEG, Trinity College Dublin

Mobile: +420-777-218-122

On Mon, Nov 21, 2016 at 3:31 PM, Ján Husarčík <> wrote:

Hello,

in http://docs.oasis-open.org/xliff/xliff-core/v2.1/csprd01/xliff-core-v2.1-csprd01.html#annotations (4.7.3.1.1 Translate Annotation), it's not clear how to correctly use combination of inline codes  and <mrk>.

For example, while 

<mrk id="1" translate="no"><pc id="1">bold</pc> text</mrk>

should be equivalent to 
<pc id="1"><sm id="n1" translate="no">bold</pc> text<em startRef="m1">

one can choose to implement it as 
<mrk id="1" translate="no"><pc id="1" canCopy="no" canDelete="no" canReorder="no">bold</pc> text</mrk>

would it be possible to provide additional guidance as a Note?

Thanks,

Jan