• State Suggested Answer
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 64 subscribers
  • Views 3457 views
  • Users 0 members are here
Options
Related

"How to" or "best practices" for working with varieties/variations

Nils Jörn

Hello,

we are new to SDL Passolo and we didn't work with varieties/variations in the past.

Now we must start using variations in our projects.

Therefore we are searching for a "how to" or "best practices" on how to start with.

We already know, how to add variations to a project.

But as far as we know right now, there are two possibilities for working with variations :

1.) Add a variation to the project and "transfer" all translations from the main language to the variation. And then translate all strings, which are variation specific.

2.) Creat a satelite assembly which contains only the strings that don't match the strings in the main language and translate these strings.

Our main questions are:

According to 1.): How do we get all the translations from the main language into the variations? And if there are all strings included: How does the translator know, which of all these strings shall be translated into a specific variation?

And according to 2.): How to we get only the strings into the variation, which shall be translated?

I hope, you'll understand what I mean.

If you have any further questions, please don't hesitate to contact me.

Thank you very much in advance.

Kind regards and stay safe.

Nils
Rate translation
×
Suggest better translation
×
Parents
  • 0

    Mmmh, long story. Before sending an answer, I would like to clarify the word varieties, which I think should be variations.

    Let me try to rephrase your problem, maybe there are other Passolo user out there that work with variations and can contribute their solutions. Let’s assume you localize your software e.g. from DE to FR. Now a special OEM client will  buy your software but needs a different French translation. Most of the translations are correct, but changes are required for product names, some terms, some phrases. Is this want you define as a variety (or variation)?
  • 0 in reply to Achim Herrmann

    Hello Mr Herrmann,

    thank you very much for your answers and for clarifying the words.

    Yes, what I've defined as "variety" - or "variation" - is exactly that: most of the translations are correct and only some terms or phrases require a different translation.

    Kind regards
  • 0 in reply to Nils Jörn

    The answer is quite simple, most of the clients don’t have to localize products that have variations. So such a feature was requested very rarely and for the clients that really need it I developed a customized solution. Another solution approach that can be used is the Leverage feature.

    Although SDL is localizing its Windows desktop based products like SDL MultiTerm or SDL Trados Studio using SDL Passolo, none of these products have variations. So I can’t give a generic advice on how to work with variations. Clients have different business need and processes, so all advices are quite specific.

    There are clients that create a copy of the SDL Passolo project file, then delete the unnecessary target languages  before starting to vary the translations in the language that the OEM client requested. That makes sense if your OEM client want to do the translation changes themselves and because many of the OEM products also differs in code. Using Leverage or Pre-Translation updates of the OEM product can be taken over from the original product LPU.

    It might be possible to create a variation of the translations by inserting another language into the project. (Original: EN->DE, FR || Enhanced: EN->DE, FR, fr-FR for OEM). Depending on the development environment and the localization concepts used this also might have an impact on the way how target file are created and will require that all source modules are the same.
Reply
  • 0 in reply to Nils Jörn

    The answer is quite simple, most of the clients don’t have to localize products that have variations. So such a feature was requested very rarely and for the clients that really need it I developed a customized solution. Another solution approach that can be used is the Leverage feature.

    Although SDL is localizing its Windows desktop based products like SDL MultiTerm or SDL Trados Studio using SDL Passolo, none of these products have variations. So I can’t give a generic advice on how to work with variations. Clients have different business need and processes, so all advices are quite specific.

    There are clients that create a copy of the SDL Passolo project file, then delete the unnecessary target languages  before starting to vary the translations in the language that the OEM client requested. That makes sense if your OEM client want to do the translation changes themselves and because many of the OEM products also differs in code. Using Leverage or Pre-Translation updates of the OEM product can be taken over from the original product LPU.

    It might be possible to create a variation of the translations by inserting another language into the project. (Original: EN->DE, FR || Enhanced: EN->DE, FR, fr-FR for OEM). Depending on the development environment and the localization concepts used this also might have an impact on the way how target file are created and will require that all source modules are the same.
Children
No Data