Project

General

Profile

Feature #580

'Dirty' translations detection

Added by Marko Kastelic over 9 years ago. Updated about 7 years ago.

Status:
Assigned
Priority:
Normal
Assignee:
-
Start date:
07/02/2010
Due date:
% Done:

0%

Estimated time:
Complexity:
Normal

Description

Translator basicaly uses two languages, origin (from) and target (to). Let's suppose that translation got to 100%.
If after that time one or more variables from origin were changed, the translator has no tool to detect such changes; translation stays at 100%.
In such a cases, changed language variable should be marked as dirty, thus giving the translator an alarm that she/he has to revise the translation, confirm the current translation or make on appropriate change.
Dirty state can be accieved by comparing dates of the last change (already integrated as far i can see), visualized (eq. yellow dot at the right most column of the translation table), selected (filter; eq. add dirty besedi translated, untranslated), ...


Related issues

Related to CDA - To do #556: Refactor CDAFeature implemented27/01/2010

Actions

History

#1

Updated by Yannick Warnier over 9 years ago

This is a very valid suggestion you make here. It has already generated a lot of translation problems in the past. I think the term to be used should be "invalidate" the translation, instead of marking it as "dirty", but it is a very good idea anyway.

This should be possible for all languages (not only English) as a few local languages (like Catalán and Asturian) are translated directly from Spanish, so if the Spanish translation is modified, the translator from Spanish to Catalán should have the variable marked as "untranslated" or something like that.

This could help the translation quality process tremendously.

#2

Updated by Hans De Bisschop over 9 years ago

  • Status changed from New to Assigned
  • Assignee set to Hans De Bisschop

A very valid suggestion which is downright easy to implement, given the structure we currently have. Perhaps the unvalidated translations should also be excluded from the progress-bar.

Thanks for the suggestion Marko !

#3

Updated by Marko Kastelic over 9 years ago

i do not like the term invalidate; it is or it is not. Translation can stil be correct/the right one and used further without a change. "out of date" or "outmoded" may be better.

#4

Updated by Yannick Warnier over 9 years ago

Agreed. "Outdated" seems better to me.

#5

Updated by Hans De Bisschop over 9 years ago

  • % Done changed from 0 to 80

Implemented most of this today (it's in the repository, not yet in the live version).

Available features:
- Status column for languages, whether or not the language contains any outdated translations
- Status column for language packs, whether or not the language pack contains any outdated translations
- Status column for translations, whether or not the translation is outdated
- "Verify" and "Depricate" actions to either set or unset the translation as outdated. I added the depricate because at times you may know a translation is no longer accurate, but you might not know a suitable alternative straight away.
- An extra filter for language packs to show only those translations which are outdated

... and I get the feeling I've forgotten something.

#6

Updated by Stefaan Vanbillemont over 8 years ago

  • Target version set to 2.1.0
#7

Updated by Sven Vanpoucke over 8 years ago

  • Target version changed from 2.1.0 to 82
#8

Updated by Stefaan Vanbillemont over 8 years ago

  • Target version changed from 82 to Backlog (default)
#9

Updated by Stefaan Vanbillemont over 7 years ago

  • Assignee deleted (Hans De Bisschop)
#10

Updated by Stefaan Vanbillemont about 7 years ago

  • % Done changed from 80 to 0

Also available in: Atom PDF