[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xliff-comment] XLIFF 2.1 csprd01: Translate Annotation and inline elements
Thanks,Maybe this and other rendering rules/requirements could be considered as a module for next version.Hello David,I would like to retract https://issues.oasis-open.org/browse/XLIFF-16 , as does not address the whole problem.
JanOn Mon, Nov 21, 2016 at 7:56 PM, David Filip <david.filip@adaptcentre.ie> wrote:Thanks, Jano,please follow the disposition here:Any comments please post in this threadCheers and thanksdFDr. David Filip===========OASIS XLIFF OMOS TC ChairOASIS XLIFF TC Secretary, Editor, Liaison OfficerSpokes Research FellowADAPT CentreKDEG, Trinity College DublinMobile: +420-777-218-122On Mon, Nov 21, 2016 at 3:31 PM, Ján Husarčík <jan.husarcik@gmail.com> wrote:JanThanks,would it be possible to provide additional guidance as a Note?one can choose to implement it asshould be equivalent to<mrk id="1" translate="no"><pc id="1">bold</pc> text</mrk>Hello,For example, while
in http://docs.oasis-open.org/xliff/xliff-core/v2.1/csprd01/xli (4.7.3.1.1 Translate Annotation), it's not clear how to correctly use combination of inline codes and <mrk>.ff-core-v2.1-csprd01.html#anno tations
<pc id="1"><sm id="n1" translate="no">bold</pc> text<em startRef="m1">
<mrk id="1" translate="no"><pc id="1" canCopy="no" canDelete="no" canReorder="no">bold</pc> text</mrk>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]