• State Verified Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 430 subscribers
  • Views 821 views
  • Users 0 members are here
Options
Related

Translating multi-lingual Passolo project in Trados

bfj document services

We have a UI localization project (dll files)  in Passolo into 12 languages. As most of our translators only have Trados to work with, we need to process the files there.


What's the best way to handle that with Trados 2017? I'd like to have one mulit-lingual project in Trados containing all languages but from Passolo I need to export one file for each language - which means I don't have a single source file for Passolo but 12 different files, one for each language. Can Trados handle something like that or do I really need to create 12 different projects?

 

Thanks

yve

 
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    Hello ,

    Unfortunately it is not possible to export a multilingual project in the version of Passolo that you have.
    This leaves two options-

    1) You could export 12*SDLXLIFF's and then create 12 separate projects-
    Ideally the freelancer should be able to see the kontext and read the dialogue that is often held in the DLL's- Through this workflow this is not possible- meaning you will have to update all the files/re-size etc. once these are returned to you, increasing time and costs.

    2) If you upgrade your current Passolo version to the 'Team Edition' you will be able to send out proper Passolo projects (removing very inefficient workarounds) to your translators who in turn can use the FREE Passolo Translators Edition-.
    This is most definitely the suggested solution for a clean and efficient workflow when working with external translators.

    Oana Nagy | QA Engineer | RWS Group

  • 0 in reply to Oana Nagy

    Thank you, Steven.

    I used the xsliff export as you suggested - but I have put all languages into one project because the different files already have the language information in them and separate TMs can be assigend for each language, great thing. Hope it will work like this.

    However, there is an information message displayed for the file type: "Diese Datei wurde ohne Verwendung einer Dateitypdefinition erstellt. Die folgenden Funktionen stehen nur eingeschränkt zur Verfügung (..)".

    However, everything seems to work, for the translators,too. How can it be that a SDL-internal format does not automatically have the correct file type definition with it? How can I get rid of it?

     

     

Reply
  • 0 in reply to Oana Nagy

    Thank you, Steven.

    I used the xsliff export as you suggested - but I have put all languages into one project because the different files already have the language information in them and separate TMs can be assigend for each language, great thing. Hope it will work like this.

    However, there is an information message displayed for the file type: "Diese Datei wurde ohne Verwendung einer Dateitypdefinition erstellt. Die folgenden Funktionen stehen nur eingeschränkt zur Verfügung (..)".

    However, everything seems to work, for the translators,too. How can it be that a SDL-internal format does not automatically have the correct file type definition with it? How can I get rid of it?

     

     

Children
No Data