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:
greeting=Hello

source file v2:
greeting=Hello World

trans file v1:
greeting=Hallo

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):
2.0.0

How reproducible:

Steps to Reproduce:
1. Push both files above
2. Pull the translation
  
Actual results:

(To be tested)

Expected results:
greeting should be untranslated

Additional info:

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.