[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xliff] ITS: Preserve space and Language Information
urn:oasis:names:tc:xliff:its:2.1
HI Yves, David, all,one clarification question: Yves used in his examples the its:lang and its:space attributes. Is the idea to add things to the OASIS to be hosted ITS namespace or to add attributes to the W3C ITS namespaces? In the past we discussed the former.Best,FelixAm 24.10.2014 um 10:55 schrieb Dr. David Filip <David.Filip@ul.ie>:Thanks, Yves, inlineOn Fri, Oct 24, 2014 at 3:31 PM, Yves Savourel <ysavourel@enlaso.com> wrote:I agreeI don't understand what losing granularity means, as I understand granularity, you get more of it IMHO, if you make whitespace handling and language info structural..Anyways, I see your point that it is not ideal to force Extractors to segment in order to handle a relatively frequent extraction issue.And i do see value in deferring the segmentation issues by putting the its info inline..YesYes, we cannot
And I think it is actually better to have the inline semantics of these attributes defined in one module..So I am OK with defining those two attributes in the its module namespaceStill, as I said in the other thread, I'd keep the informative description of what you can do with core only, of course moved into the partial support section..CheersdFDr. David Filip=======================OASIS XLIFF TC Secretary, Editor, and Liaison OfficerLRC | CNGL | CSISUniversity of Limerick, Irelandtelephone: +353-6120-2781cellphone: +353-86-0222-158facsimile: +353-6120-2734mailto: david.filip@ul.ie
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]