Next in thread → Next in month →

1.2 to 2.0 Gaps and Proposals

From
Ryan King
Date
2013-01-19T00:46:00+00:00
ID
Thread
1.2 to 2.0 Gaps and Proposals
+1 For the proposal as Yves outlines it.  Just a note on the types and definitions, however. Going from my experience, which I understand is not everyone's experience, you can have a tm that stores an entire XLIFF document, not just segments from the document. In this way, it is entirely possible that your 100% match can be from a tm and be either exact (segment match) or in context (contextual match). In your list below tm and icm are mutually exclusive. However, using the subtype attribute, you could define type="tm" and subtype="abc:exact" or subtype="abc:context" (I'll avoid calling it ice here), so I think this proposal will cover the scenario adequately.  Thanks, ryan
Next in thread → Next in month →