Subject: RE: [xliff] Call For Dissent re csprd03 re 206
If you want to get picky, the annotation actually overrides the value of the translate attribute of the closest ancestor element that can have translate: it can be unit (in most cases) but it can be another <mrk> too.
Thanks, Yves, I was about to implement it but came with a better, more precise formulation
This annotation overrides the translate attribute set or inherited at the <unit> level.
The rationale is that the default inline value is always inherited from unit, no matter if it was set or inherited at the unit level.
So I'd move the deadline for the CFD to next Monday
I am going going to implement today anyway as it is indeed minor
On Wed, Mar 5, 2014 at 2:12 PM, Yves Savourel <email@example.com> wrote:
The solution looks OK to me.
This is to propose a solution for the comment 206 by Yves.
I suggest that the Note is changed as follows:
This annotation overrides the translate attribute set at the <segment> level.
This annotation overrides the translate attribute set at or inherited from the <unit> level.
I will consider this solution approved unless I hear otherwise by the end of this week.
I plan to tentatively implement this solution into the spec during tomorrow