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: RE: [xliff] xml:lang

Hi David, all,


I assume that for target you meant to write:


“the value defined by the trgLang attribute on <file>.”


Also for the constraint: There is no reason to forbid xml:lang on elements that do not affect the <source> and <target> inheritance. For example one may want to specify the language of a <note> element. So xml:lang should be prohibited only on <file>, <group> and <unit>. And, I suppose, on <mtc:match>.






From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Dr. David Filip
Sent: Tuesday, January 21, 2014 5:00 AM
To: xliff@lists.oasis-open.org
Subject: [xliff] xml:lang


Hello all, I promised I will be back with a proposal for xml:lang that we have so far neglected as the discussion concentrated on xml:space.



I believe that the following should be done



xml:lang defaults should be changed 

for source:

to value defined in srcLang on the xliff elemenet


for target:




Currently, people not defining xml:lang on source or target leave it undefined, which is clearly wrong


Adding a Constraint


xml:lang MUST NOT be set at core extension points.



Setting the value would conflict with srcLang and trgLang semantics




I am going to implement and print this before the meeting, please shout no later than in the meeting if you think this is wrong or you have a better solution










Dr. David Filip



University of Limerick, Ireland

telephone: +353-6120-2781

cellphone: +353-86-0222-158

facsimile: +353-6120-2734

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