Hi Stepan Konev

I know you are asking for videos or articles, but I can tell you one clear reason why Passolo is necessary.

In Passolo, all strings are managed by parameters such as source paths, source file names, string IDs, source text, etc. All these parameters can be used when legacy translation is leveraged, i.e. all legacy strings are not being simply translated using TM, rather they are leveraged using all or any of those parameters and you can choose which parameters should be used.

For example, there are plural forms and some languages will require the following plural forms translated uniquely. In non-Passolo workflow, TM will be applied to source text "Open Cases" without context re: how many cases translation is for, and translation will be the same for all "Open Cases." This could result in inaccurate translation. 

In Passolo workflow, string ID such as "zero" and "few", etc. can be used as parameters and apply the correct legacy translation for each "Open Cases" source text. In many target languages, they should be translated differently.

in certain industries such as life science where FDA approvals are important part of software development, maintaining legacy translation correctly is a must. 

I hope it helps.

Thanks,

Naoko

Hi Stepan Konev

I know you are asking for videos or articles, but I can tell you one clear reason why Passolo is necessary.

In Passolo, all strings are managed by parameters such as source paths, source file names, string IDs, source text, etc. All these parameters can be used when legacy translation is leveraged, i.e. all legacy strings are not being simply translated using TM, rather they are leveraged using all or any of those parameters and you can choose which parameters should be used.

For example, there are plural forms and some languages will require the following plural forms translated uniquely. In non-Passolo workflow, TM will be applied to source text "Open Cases" without context re: how many cases translation is for, and translation will be the same for all "Open Cases." This could result in inaccurate translation. 

In Passolo workflow, string ID such as "zero" and "few", etc. can be used as parameters and apply the correct legacy translation for each "Open Cases" source text. In many target languages, they should be translated differently.

in certain industries such as life science where FDA approvals are important part of software development, maintaining legacy translation correctly is a must. 

I hope it helps.

Thanks,

Naoko

Naoko-san, thank you for your input.
It seems I have never received jobs with such parameters (but I understand what you mean—this is relevant for the Russian language). When I tried using Passolo directly, I only had a simple text editor lacking all useful features (like termbase, autosuggest, etc.) that I have got used to. That's why I am trying to assume now whether learning Passolo is worth the effort. Thanks again.