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] Match type and subType


hi Ryan,

> 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.

The type 'tm' does not indicate an exact match, just a match coming from a translation memory without other specific qualifier. So if your match is coming from a TM and is contextual, one would use 'icm'.

Exactness is indicated by the similarity attribute.

cheers,
-yves



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