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

[Rodolfo M. Raya]

On Thu, 2005-02-17 at 14:36 +0100, Josep Condal wrote:

Hi,

> 1. There is no target element.
> 2. The state attribute is "needs-translation".
> 
> Only the latter allows for the concept of fuzzy-pretranslation (like in
> SDLX or Trados, where a segment of the memory is primed into the
> bilingual file as proposal for the given segment, normaly at
> pretranslation time).

If the translation tool notices that there is no <target> or that an
existing <target> is empty, it can check the TM database and offer
translations, without verifying the value in the "state" attribute. Why
do you say that only having state set to "needs-translation" allows for
the concept of fuzzy-pretranslation?

Heartsmome's XLIFF editor checks the database every time you visit a
segment that is not approved, with empty target and no 100% matches
offered as suggested translation. All this without looking at the
"state" attribute at all.

The best a CAT tool can do for a translator is offer matches. This
should not be restricted.

Regards,
Rodolfo
-- 
Rodolfo M. Raya <rodolfo at heartsome.net>
Heartsome Holdings Pte. Ltd.