OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xliff-comment message

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


Subject: RE: [xliff-comment] XLIFF 2.0 Core finished?



> -----Original Message-----
> From: Yves Savourel [mailto:yves@opentag.com]
> Sent: Tuesday, May 22, 2012 6:00 PM
> To: 'Rodolfo M. Raya'; 'Pål Eivind J Nes'
> Cc: 'Josep Condal'; xliff-comment@lists.oasis-open.org
> Subject: RE: [xliff-comment] XLIFF 2.0 Core finished?
> 
> > If a user does not want to translate a segment, then user  can leave
> > the segment with just <source> and no <target>. There is nothing wrong
> > with that.
> 
> There is nothing in 1.2 that say how to interpret <trans-unit> with no
> <target>. Therefore leaving it missing has no predictable behavior. That's
> IMO not a good thing. E.g some merger may use the source, other may use
> an empty string.

That's a tool choice, not a specification problem. 

> I think we have already some text for this in 2.0. If not we should (especially
> because of <ignorable>).

XLIFF 2.0 defines what is to be considered translated but doesn't say how to process untranslated segments. 

Regards,
Rodolfo
--
Rodolfo M. Raya       rmraya@maxprograms.com
Maxprograms       http://www.maxprograms.com



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