Bug 1086043 - Previous translations show up in TM results
Summary: Previous translations show up in TM results
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Zanata
Classification: Retired
Component: Component-UI
Version: 3.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Patrick Huang
QA Contact: Zanata-QA Mailling List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-10 01:43 UTC by Hedda Peters
Modified: 2023-09-14 02:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-07-29 03:34:33 UTC
Embargoed:


Attachments (Terms of Use)

Description Hedda Peters 2014-04-10 01:43:08 UTC
Description of problem:
The TM shows previous translations for a particular string, not only the most recent translation. Neither the English string nor the translation that is shown in the TM actually exist in Zanata anymore, they have both since been updated. Yet, they are presented as TM results. 

How reproducible:
always

Steps to Reproduce:
see next comment (private) with links

Actual results:
The current and previous versions of a matching string are shown in the TM results. Moreover, the previous version is shown higher up than the current version.

Expected results:
Only the current version of a matching string should be shown. 


Additional info:
Strings get updated for a reason, e.g. correcting a mistake in the translation. There is no benefit of showing those previous translations in the TM, it only opens a door to reusing wrong translations.

Comment 3 Patrick Huang 2014-04-30 03:18:49 UTC
Is this fixed in latest copyTran implementation?

Comment 4 Zanata Migrator 2015-07-29 03:34:33 UTC
Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-328

Comment 5 Red Hat Bugzilla 2023-09-14 02:06:07 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.