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

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

Parents Reply
  • 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

Children