[zanata-bugs] [Bug 1025574] Status of pre-existed translation string changes from "translated" to "fuzzy" when pushing source+target with CopyTrans disabled

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1025574



--- Comment #3 from Yuko Katabami <ykatabam at redhat.com> ---
Hi Sean,

(In reply to Sean Flanigan from comment #2)
> Pushing source and targets can easily change the target status from
> translated to fuzzy:
> 
> 1. When pushing target files for PO projects, the messages may be marked as
> fuzzy, in which case they will become fuzzy on the server.  That doesn't
> apply here, because I think this project uses Properties files.
> 
> 2. When pushing source files for Properties/XLIFF projects, the English text
> for a given property key may change.  When that happens, all the target
> strings will be marked as fuzzy, because they are translations of the old
> string, not the new one.
> 

> 
> But in this case, the target files were pushed too, and assuming the target
> file actually contained a translation for the affected string (can you
> double-check that please, Yuko?) it should perhaps have replaced the fuzzy
> string with an approved one.

I have confirmed that most recently pushed file contains the same translation
string as the previous file.

> 
> However, it looks like the class TranslationMergeAuto is does not overwrite
> the translation because it found the same content in the history of the
> HTextFlowTarget.  
> 
> 
> Yuko, are you able to provide the old and new version of the files which
> were uploaded?  If the English source text was changed, I would have
> expected the translation text to change too in most cases.  If the
> translation text did not change, the merge=auto algorithm may reject it,
> because it probably needs to be updated, or at least reviewed.  Importing
> the old string over the fuzzy string could mask an outdated translation. 
> (Properties files are a very poor localisation format, because you can't
> always be sure what a target string was translated from.  All you get is the
> property key.  This is our attempt to defend against some of the risks.)

I will be emailing files.

> 
> By the way, Yuko, I think 3.0.3 is the version of Maven, but it may not be
> the version of zanata-maven-plugin.  The version of zanata-maven-plugin
> should have been logged at runtime.

I see. Please let me know how I can find it.


Kind regards,

Yuko

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=2cEM9U6bkq&a=cc_unsubscribe