Bug 873489
Summary: | XLIFF/Properties/PO upload should check that translations correspond to the current text flow contents | ||
---|---|---|---|
Product: | [Retired] Zanata | Reporter: | Sean Flanigan <sflaniga> |
Component: | Component-Logic | Assignee: | Sean Flanigan <sflaniga> |
Status: | CLOSED UPSTREAM | QA Contact: | Zanata-QA Mailling List <zanata-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | damason, dchen, mkim, pahuang, zanata-bugs |
Target Milestone: | --- | Keywords: | screened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-07-29 03:35:34 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Sean Flanigan
2012-11-06 01:13:16 UTC
See bug 873500 for Properties files. We should add sourceContentHash to TextFlowTarget, and have the XLIFF and Properties clients pass a hash of the source content. Then the server could verify that the sourceContentHash matches the current version of the HTextFlow, else reject the translation. *** Bug 873500 has been marked as a duplicate of this bug. *** *** Bug 873930 has been marked as a duplicate of this bug. *** As of Zanata 3.2.0, TextFlowTarget includes a sourceHash property. If sourceHash is provided, TranslatedDocResourceService on the server will check that the sourceHash matches the HTextFlow before persisting the HTextFlowTarget. The gettext formats (including offlinepo) now provide sourceHash when pushing to the server, but this still needs to be implemented for xliff and properties files. Pull request (WIP): https://github.com/zanata/zanata-common/pull/1 Both pull requests have been updated. Note that the required changes for PO files were in server commit 0a3971e, common commit 24c7951 and client commit 880c69a157. Source content checking for PO files requires client >= 3.2.0, and only works with Zanata server >= 3.2.0. (Note that there was no bz for that change.) We have similar bug 1194543 that is implementing the solution for formats that use positional identifiers. (In reply to Michelle Kim from comment #10) > We have similar bug 1194543 that is implementing the solution for formats > that use positional identifiers. That bug is about source text that changes which identifier it uses (e.g. due to position change), but this bug is about translations being pushed that were translated from an old version of the source. I do not think they are related since the cause and the fixes for them are different. Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-336 |