[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xliff] [csprd02 139] CFD: Propose Change Track is allowed on <xliff>, <group>, and <unit>.
Oh, right. Makes sense. So I guess we’ve cleared CFD. Ryan has given me the go-ahead to make the updates. From: Dr. David Filip [mailto:David.Filip@ul.ie]
By resulting I mean the same what you mean, i.e. correcting the mistake and replacing <xliff> with <file> in the set of elements, where the module is to be allowed..
Dr. David Filip ======================= LRC | CNGL | LT-Web | CSIS University of Limerick, Ireland telephone: +353-6120-2781 cellphone: +353-86-0222-158 facsimile: +353-6120-2734 mailto:
david.filip@ul.ie On Fri, Dec 13, 2013 at 5:21 PM, Schnabel, Bryan S <bryan.s.schnabel@tektronix.com> wrote: Yes, again I misfired. I agree the right elements to allow ctr are "**<file>**, <group> and <unit>"
not "in **<xliff>**, <group> and <unit>." That was a typo on my part. But David I don’t understand “this module should be explicitly allowed on the resulting set of elements.” Can you elaborate, or let me know if this changes my proposal? From: Dr. David Filip [mailto:David.Filip@ul.ie]
I agree with Yves and also agree that this module should be explicitly allowed on the resulting set of elements Rgds dF
Dr. David Filip ======================= LRC | CNGL | LT-Web | CSIS University of Limerick, Ireland telephone: +353-6120-2781 cellphone:
+353-86-0222-158 facsimile: +353-6120-2734 mailto:
david.filip@ul.ie On Tue, Dec 10, 2013 at 9:04 PM, Yves Savourel <ysavourel@enlaso.com> wrote: Hi Bryan, Ryan, all,
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]