[xliff-tools] The Fuzzy Flag

[Tim Foster]

On Wed, 2005-02-16 at 15:05, Bruno Haible wrote:
> This flag also occurs as side effect from msgmerge. I would therefore
> not use the <target> element in this case, and instead give
> <alt-trans><source>...</source> <target>...</target></alt-trans>

+1

 - putting translations in the <target> element I think should be
something that only a human can do. We allow 100% matches in there, but
don't mark the segment as being approved until a human does so (possibly
via the "Approve All Segments" option, but even still, they have to take
some action to make it so.

We wanted to make our xliff files as foolproof as possible, so that someone
would really have to go to some trouble to unwittingly take a partially
translated xliff file and import it into a database without the 
translation being complete.

(the risk being, of course, that other projects could leverage from
incomplete or unreviewed translations)

> (The XLIFF translation editors are expected to give an easy way to copy
> the contents of an <alt-trans> element into the <trans-unit> that contains
> it.)

Yep - we have that alright :-)

	cheers,
			tim

-- 
Tim Foster - Tools Engineer, Software Globalisation
http://sunweb.ireland/~timf http://blogs.sun.com/timf
http://www.netsoc.ucd.ie/~timf