The first sentence leads me to believe that Passolo is not being used correctly for the use case described.

When you receive a new resource file from the development, you naturally want to know what the developers have changed. However, this does not work by adding the file to the project as a new resource and then aligning the old translations.

The best practice would be to simply replace the old resource file with the new one and then update the existing project. A report is then available showing what has changed or has been added and all these entries are marked in the source string list.

Hi Achim, 

The case it's the programmer change the source but also the translation. Can be a request by the customer or the specification to create this new dialog contains the translated string, 

We want to retrieve the new translation from the programmer to validate the new source and the new translation from the programmer. 

have a nice day 

Hi Achim, 

The case it's the programmer change the source but also the translation. Can be a request by the customer or the specification to create this new dialog contains the translated string, 

We want to retrieve the new translation from the programmer to validate the new source and the new translation from the programmer. 

have a nice day 

Developers changing both the source files and the translated files outside the chosen localization tool is not really best practice, but it happens in real life.

However, my proposed best practice approach should be followed. After updating the source files of the project, changed and new text entries of the developers can be detected and filtered.

In a further process step, the translated file, which has also been changed by the developers, can then be aligned. A date filter can then be used to determine and filter which translated entries the developers have changed.