Bug 1225236 - Improving translation of duplicate strings that may or may not have a different context
Summary: Improving translation of duplicate strings that may or may not have a differe...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Zanata
Classification: Retired
Component: Component-Logic
Version: development
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Damian Jansen
QA Contact: Zanata-QA Mailling List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-26 22:31 UTC by Isaac Rooskov
Modified: 2015-08-06 05:55 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-07-28 23:14:43 UTC
Embargoed:


Attachments (Terms of Use)

Description Isaac Rooskov 2015-05-26 22:31:42 UTC
Description of problem:

In some Zanata projects we will have the same English string repeated multiple times, which may lead to different translations for the same string. While some times this may be intentional due to context differences, sometimes this may be an error. 

A possible solution from Christophe (cfergeau):
"This looks like something which would not be that hard
with the appropriate tools. Zanata (or some separate tool) could have a
view only showing strings (+ translations) which are duplicated,
translators would be able to review these strings, and could easily spot
the source strings which are needlessly duplicated. Once you have a list
of strings which should have a common translation, this can be given to
the developers and fixed."

Comment 1 croe@redhat.com 2015-05-26 22:57:23 UTC
This should not be difficult to solve now that Admin and User Portal strings have been merged into a single file, oVirt (master).

Could we extract these duplicate strings in an automated fashion please?

Comment 2 Luke Brooker 2015-06-05 12:14:20 UTC
Another way this could be solved in Zanata is by auto-filling duplicate translations once one has been translated, referencing the original translation. That way it can always be reviewed later in case it is in a different context.

Another option could be to group them together under one translation.

This will always be better done by developers, but a lot of times they will miss this, so something in Zanata will help.

Would these options solve the problem?

Comment 3 croe@redhat.com 2015-07-06 00:35:08 UTC
'auto-filling duplicate translations once one has been translated' is what is currently used by other translation softwares like SDLX and MemoQ. You may which to auto-fill but save them as Fuzzies to allow context discrepancy control.

Comment 6 Zanata Migrator 2015-07-28 23:14:43 UTC
Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-78


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