Bug 831035
| Summary: | RFE: On-Demand copy trans. | ||
|---|---|---|---|
| Product: | [Retired] Zanata | Reporter: | Carlos Munoz <camunoz> |
| Component: | Component-Logic, Usability | Assignee: | Carlos Munoz <camunoz> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Ding-Yi Chen <dchen> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 1.7 | CC: | sflaniga, zanata-bugs |
| Target Milestone: | --- | ||
| Target Release: | 1.7 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 1.7-SNAPSHOT (20120705-0026) | Doc Type: | Bug Fix |
| Doc Text: |
Cause
Zanata was only able to run the translation copy mechanism on newly pushed documents and used a very conservative algorithm to find matches (same document name, same translation context and content).
Consequence
Project Maintainers were only able to invoke the translation copy functionality at the same time they were pushing documents. Also, this meant that maintainers were not able to reuse some potentially reusable translations (such as those that belong to documents that moved to a different directory).
Change
Implemented an option for Project Maintainers to invoke a translation copy from the GUI (project version page).
Result
Project maintainers are now able to invoke a translation copy at any time, with some customization options. Since the process is now applicable to already existing documents, Zanata makes sure that only a single Copy Trans is running at any given time for a project version, and will prevent any user from starting another copy trans if another is in progress. It will also show progress information for any ongoing translation copies for a project version.
Also, project maintainers are now able to slightly customize the sensitivity of copy trans. The user can select which actions to take when a translation matches, but its document name or its context doesn't, entirely disregarding the translation, reusing it but marking it fuzzy, or ignoring the mismatch and reusing it.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-09-11 05:11:32 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
Carlos Munoz
2012-06-12 04:44:33 UTC
Initial implementation. See: https://github.com/zanata/zanata/commit/f2d24015c532b1ef5af13f70a0db2cee68c56755 Added copy trans options and progress feedback for project maintainers. The project version page will show if there is currently a copy trans running for the select version, and will also show a progress bar, number of documents processed, estimated time remaining, and the user that started the copy trans. Additionally, the user will be able to cancel the copy trans, and the system will now enforce that only a single copy trans should be running at any given time for a project version. See: https://github.com/zanata/zanata/commit/921adcecc487c349071e33f77523856a87c59fea https://github.com/zanata/zanata/commit/da7287f966cb3993f4c1cd2f8fb4a28ab8741437 https://github.com/zanata/zanata/commit/d24ba2fb747e32b73b1629a34126c8617ab58e76 https://github.com/zanata/zanata/commit/a12eb39eb99bb0da860a80c0a821143dbed6e8f8 https://github.com/zanata/zanata/commit/b031146696bf4f6965d9903bed73ea5edd8b4d8b https://github.com/zanata/zanata/commit/cefeb811d05b8b9cd727fcf8cdca5ca0658b8ae1 https://github.com/zanata/zanata/commit/0e780595b09fda78e8b26d1517d0e99dfa45d15d https://github.com/zanata/zanata/commit/f2d24015c532b1ef5af13f70a0db2cee68c56755 Testing Notes: - Only a single copy trans should be available to run at any time for a project iteration. Zanata should prevent two copy trans from running simultaneously for the same version. - Multiple users should be able to see the progress of an ongoing copy trans. As soon as the copy trans finishes (and if the user has the appropriate permissions), they should see a button to start another copy trans.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Cause
Zanata was only able to run the translation copy mechanism on newly pushed documents and used a very conservative algorithm to find matches (same document name, same translation context and content).
Consequence
Project Maintainers were only able to invoke the translation copy functionality at the same time they were pushing documents. Also, this meant that maintainers were not able to reuse some potentially reusable translations (such as those that belong to documents that moved to a different directory).
Change
Implemented an option for Project Maintainers to invoke a translation copy from the GUI (project version page).
Result
Project maintainers are now able to invoke a translation copy at any time, with some customization options. Since the process is now applicable to already existing documents, Zanata makes sure that only a single Copy Trans is running at any given time for a project version, and will prevent any user from starting another copy trans if another is in progress. It will also show progress information for any ongoing translation copies for a project version.
Also, project maintainers are now able to slightly customize the sensitivity of copy trans. The user can select which actions to take when a translation matches, but its document name or its context doesn't, entirely disregarding the translation, reusing it but marking it fuzzy, or ignoring the mismatch and reusing it.
VERIFIED with Zanata version 1.7-SNAPSHOT (20120705-0026) |