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] XLIFF 2.0 Core

Hi Rodolfo, all,

Thanks for the XSD, it's very handy.

I like the more specific <match> instead of the all-purpose <alt-trans>.
It makes sense to specialize the elements.
But I don't think candidate matches should be part of the core. (Same for <note>).
To me the core would be just the data needed to extract, translate and merge, with possibly a few meta-data like resname, restype, etc. that could be considered as basic properties.

Another though about <match>: We probably need to handle also the cases where there are match candidates offer for both the whole unit and for each segment, instead of just for each segment. Tools like WorldServer offer such feature for example. 

Handling the "outside" extra spaces/codes with <ignorable> looks good.
Do we have a case for allowing multiple <ignorable> at each ends? I cannot think of any tool that would have more than one inter-segment span. Not a big issue: allowing 0 or more just makes it a bit less simple to handle.


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