• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 20 replies
  • Answers 1 answer
  • Subscribers 433 subscribers
  • Views 6248 views
  • Users 0 members are here
Options
Related

What is the proper workflow to translate a .txml file in Trados?

Pavel Tsvetkov

Dear All,

I have the following situation on my hands:

1. A Client who uses Wordfast has sent to me a .txml file for translation. The requirement is to use the online Wordfast Anywhere tool (as I do not have a Wordfast license), and deliver a translated .txml file and a Wordfast TM.

2. However, I would prefer to handle the job in Trados and leverage my Trados TMs and termbases.

3. The problem is that Trados does not recognize the .txml file as a translatable file, so it is a no-go from the start. This could be yet another case of SDL refusing to recognize the file formats created by the competition in a somewhat dumb attempt to force everybody to buy Trados.

4. I could use the Word version of the source file to translate in Trados, and then manually copy the segments one by one into Wordfast Anywhere, but that would mean spending twice the time. It is not practical for bigger assignments.

5. Is there an easier workflow to follow, so that both sides would be happy? For example, is there a reliable .txml to .sdlxliff or .txml to .xliff converter that would also allow me to convert back to .txml at the end?

6. Is there any other way to solve this puzzle of proprietary file formats making our life miserable?

Best regards,

Pavel
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply Children
  • 0 in reply to Pavel Tsvetkov
    Pavel Tsvetkov said:
    How about Trados not being able to properly import bilingual Word format

    This is our own format designed for translation outside a CAT tool and not in it.  A very poor example, and clearly something that could be avoided given it's only possible to create it from Trados Studio in the first place.

    Pavel Tsvetkov said:
    I remember 5-10 years ago the "Customer is defective" mantra being used a lot in SDL's dedicated help forum on www.proz.com. I hope that is not making a comeback now.

    This has never been a mantra inside SDL.  But comments such as the one you chose to use here does seem to be something that goes on and on with little justification.

    "This could be yet another case of SDL refusing to recognize the file formats created by the competition in a somewhat dumb attempt to force everybody to buy Trados."

    Why would you even write this in a post asking for help?  Completely inaccurate and uncalled for.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Paul

    Hi Paul,

    I apologize if my initial comment has been found inappropriate or hurtful.

    When a translator has been assigned a task with a short deadline and it turns out that Trados cannot even import the source file that was created by one of the big four CAT tools today (a very popular tool indeed and a direct competitor), this definitely raises questions and on a personal level: causes a lot of stress and anguish.

    And having to download a plugin that adds the exquisite functionality of being able to open a source format... I have never come across such an implementation with another software vendor. As far as I am concerned, this is a world-first, but I am not a software developer, so this is just a personal observation: I may be wrong.

    At any rate, being forced to add such functionality by having to think of, look for, locate, download and install a separate plugin is counter intuitive, takes time, and can potentially create additional problems that are then solved by receiving help through remote sessions. More waiting, more time, work lost, more stress.

    Best regards,

    Pavel
  • 0 in reply to Pavel Tsvetkov

    You are not forced to do that at all. The job has obviously been created in another tool. The solution is to use this very tool. If you do CAT hopping, this is YOUR and solely yours responsibility to make sure, the complete process will work. Accepting a short deadline and hoping to manage without properly knowing how to is simply irresponsible. Coming to this forum and blaming others for what you should have known is not the fine English art, this is what I call moaning.

    Pavel Tsvetkov said:
    I have never come across such an implementation with another software vendor. As far as I am concerned, this is a world-first, but I am not a software developer, so this is just a personal observation: I may be wrong

    You are wrong. memoQ uses plugins for many things too.

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.