Idea Delivered

Allow Scan Target File (Alignment) to detect updated/changed translation and to set status for those as "Translated and For Review"

Hi Community,

Can you please provide an option during Scan Target File (Alignment) to detect updated/changed translation, and set status for those strings as Translated and For Review"? 

ICR/SME review doesn't always happen in TBU as desired. Instead, some clients would just make edits/changes to translation and drop the updated files for us to review. There is no simple way to identify the updated translation within Passolo after alignment.

 

In other words, I don't like the results of the current alignment - all strings are either 100% or validated, not mixed. I am sure there are pros and cons to implement this, but this option will eliminate manual work by engineers to change status for those changed to For Review. And it is so easy to change status of all strings to Validated if needed.

Thanks for considering!

Naoko

Naoko Jones
Parents

  • Hi Achim,

    Which version of Passolo has this feature been delivered?

    I am using Passolo Collaboration Edition 2018, Version 18.0.109.0, which is the latest.

    I just tested your second scenario (not so ideal world we live in) with validate translation option UNCHECKED.

    and the results I am getting is not at all what you described. In other words, if what you described is by design/specs, this has been a defect for at least 5+ years.

    After opening translation list, I sort strings by Last Change and all of the strings except for 1 (which happened to be missing in the target files I aligned against) has the exact same date & time, and all of those strings are listed as changed string in the resulting alignment report.

    There were only less than one fourth of the strings that had translation changes in the alignment file. three fourths of the strings should have stayed in the original status and with the original last change date & time, but they were all changed to pre-translated with all having the same last changed date & time, which was a few minutes before I am writing this report.

    One other weird thing is almost all stirngs now have 100% match in match column except a few strings have fuzzy match such as numbers between 75% and 99%. The origin column is indicating they come from .glo file that is attached to the project. I am guessting they are the original fuzzy match values from pre-translation, not from the alignment. That's great, but the last change is now changed to the time I aligned.

    Do I need to raise a suppor ticket for this?

    Thanks,

    Naoko

Comment

  • Hi Achim,

    Which version of Passolo has this feature been delivered?

    I am using Passolo Collaboration Edition 2018, Version 18.0.109.0, which is the latest.

    I just tested your second scenario (not so ideal world we live in) with validate translation option UNCHECKED.

    and the results I am getting is not at all what you described. In other words, if what you described is by design/specs, this has been a defect for at least 5+ years.

    After opening translation list, I sort strings by Last Change and all of the strings except for 1 (which happened to be missing in the target files I aligned against) has the exact same date & time, and all of those strings are listed as changed string in the resulting alignment report.

    There were only less than one fourth of the strings that had translation changes in the alignment file. three fourths of the strings should have stayed in the original status and with the original last change date & time, but they were all changed to pre-translated with all having the same last changed date & time, which was a few minutes before I am writing this report.

    One other weird thing is almost all stirngs now have 100% match in match column except a few strings have fuzzy match such as numbers between 75% and 99%. The origin column is indicating they come from .glo file that is attached to the project. I am guessting they are the original fuzzy match values from pre-translation, not from the alignment. That's great, but the last change is now changed to the time I aligned.

    Do I need to raise a suppor ticket for this?

    Thanks,

    Naoko

Children
No Data