[xliff-tools] PO Representation Guide: The PO Header

Asgeir Frimannsson asgeirf at redhat.com
Fri Feb 18 05:47:48 PST 2005


On Tue, 15 Feb 2005 06:08, Josep Condal wrote:
> Regarding this comment:
>  ---
>  "state" attribute of <target> element is used to qualify a translation.
> This is intended to aid project managers decide when to add a
> translation to a TM database. Look at the predefined values in
> http://www.oasis-open.org/committees/xliff/documents/xliff-specification
> .htm#state and you will understand what I mean.
>
> IMO, the "approved" attribute of <trans-unit> is better suited to
> reflect if an entry needs translation or not. If a segment needs
> translation, simply mark it as non approved. Once the translator has
> reviewed the segment, he can mark it as approved.
> ---
>
> How about if instead of the "approved" attribute we use the "translated"
> attribute?
>
> The following excerpt is from the XLIFF 1.1. specification:
> ---
> The required id
> <http://www.oasis-open.org/committees/xliff/documents/xliff-specificatio
> n.htm#id>  attribute is used to identify the <trans-unit> within the
> file. The optional approved
> <http://www.oasis-open.org/committees/xliff/documents/xliff-specificatio
> n.htm#approved>  attribute indicates whether the translation has been
> approved by a reviewer. The optional translate
> <http://www.oasis-open.org/committees/xliff/documents/xliff-specificatio
> n.htm#translate>  attribute indicates whether the <trans-unit> is to be
> translated.
> ---
>
> I I understand it right, the actual transition of the approved attribute
> from approved="no" to approved="yes" seems to be reserved for a second
> person, who reviews the translation of the translator who makes the
> transition from translated="no" to translated="yes". Obviously, if the
> translation project is not to be reviewed by a second person, the
> translator can directly approve his own translations as a shortcut.

Do you here mean the 'translate' boolean attribute of <group>, <trans-unit> 
and <bin-unit>? I couldn't find any 'translated' attribute in the 
specification. 

The 'translate' attribute can be set to 'no' to protect a <trans-unit> from 
translation. E.g. in tools such as Catalyst, these entries are read-only. Can 
e.g. be used in a customized filter where certain parts of the text is not to 
be translated (e.g. a source code example in a programming tutorial?). 

So there is no relation between the 'translate' and 'approved' attribute.

cheers,
asgeir


More information about the xliff-tools mailing list