See updates in both source and target in Passolo

In Passolo, when I import my source file and I scan the target file (alignment), is it possible to see what has been modified in both the source and the target ? 

I know that when scanning the target file, Passolo indicates in red the segments that have been added and therefore what is left to translate.

But, for example, when I receive another source file with changes in some segments, if the target segment already exists, I will not see (in red or other colour) what changes have been made to the source segment. 

Thank you for your help.

emoji
  • Hi Cindy, 

    This is the process I do when the source and the translation change and I want to validate.

    I do a Bookmark on all modify lines after I did  "Create/update string list "

    do my "Scan Target file (Alignment)"  sort the list by Last change. 

    all the change import by the alignment will be together. I do a bookmark too.

    To see what need to be validate I do a Filter by "Bookmarked strings"

    I have all the changes need to be validate.

    When my validation it's completed I remove the bookmark.

     have a nice day 

    emoji
  • 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.

    emoji
  • 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 

    emoji
  • 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.

    emoji