[xliff-tools] Approved attribute

[Bruno Haible]

Thanks for your feedback. But it's still not entirely convincing:

Rodolfo M. Raya wrote:
> The "state" attribute of the <target> element is used for controlling
> the status of a translation. 
> 
> The "approved" attribute is used to indicate whether the translation
> present in the <target> can be used or not for generating a translated
> document. This is independent of the status of a translation. 
>
> It may be necessary to generate a translated document for proofreading,
> so you can have "approved" set to "yes" and "state" set to
> "needs-review-translation" to generate a translation draft for review.

Huh? Isn't that a contradiction? The spec says "The optional 'approved'
attribute indicates whether the translation has been approved by a
reviewer." and also "Approved - Indicates whether a translation is final
or has passed its final review." So, are you assuming multiple stages
of review? If not, "needs-review-translation" should imply 'approved="no"',
no?

> You can't use an <alt-trans> element
> because you don't know what to put in the <source> element. 
> 
> In an <alt-trans> element the content of the <target> element must be a
> translation of the corresponding <source>. The original source of a 
> translation marked as fuzzy in a PO file is unknown.

But in <alt-trans> the <source> can be omitted, and the 'origin' attribute
is not required either.

Also, <alt-trans> seems better suited because there can be several of them
in a <trans-unit>: When an approximate translation is searched for in several
translation memory databases, the result will be several "alternate" or
"proposed" <target>s. The PO file can store only one approximate search
result per <source> - this is the role of the #,fuzzy flag - but when looking
at the XLIFF format in general, the way to store several approximate
matches from translation memories are several <alt-trans>, no?

Bruno