Red Hat Bugzilla – Bug 873500
Test case: Properties strategy should detect outdated translations by using source file history
Last modified: 2013-03-03 21:22:29 EST
Description of problem:
When pushing Properties content, it is possible for the translation files to have older source strings than the source files, but with the same property keys. For instance:
source file v1:
source file v2:
trans file v1:
NB: even though the ids match, "Hallo" is not a valid translation of the current v2 source "Hello World".
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Push both files above
2. Pull the translation
(To be tested)
greeting should be untranslated
It should be possible to tell (guess) that the translation "Hallo" for key "greeting" is obsolete because the v1 source "greeting" with the old string "Hello" already had the translation "Hallo".
If we change the way we generate resIds for Properties files, we will need a migration path for existing content in the database.
We have a similar problem for XLIFF files: bug 873489.
*** This bug has been marked as a duplicate of bug 873489 ***