Pavel Tsvetkov

Pavel Tsvetkov said:

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.

Or it could be yet another case of a user not knowing how to use the tools they have?

Pavel Tsvetkov said:

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?

How about this:

https://appstore.sdl.com/language/app/file-type-definition-for-wordfast-txml/247/

Also this old article may have some value for you?

https://multifarious.filkin.com/2015/03/02/converting-wordfast-resources/

In fact Pavel Tsvetkov

Pavel Tsvetkov said:

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.

What other formats do we refuse to recognize?  I can't actually think of any that I cannot handle in Trados.

Hello Pavel Tsvetkov ,

We provide a number of apps that allow you to work in Studio with various file types.

We have the following available on the SDL AppStore for TXML

appstore.sdl.com/.../

Paul said:

Or it could be yet another case of a user not knowing how to use the tools they have?

Hm, yet another plug-in to locate and install... The tool that I bought did not come with the functionality to recognize the .txml format, so, please, excuse me for not knowing that there is a plug-in I need for the purpose.

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.

How about Trados not being able to properly import bilingual Word format: https://community.sdl.com/product-groups/translationproductivity/f/studio/26216/sld-trados-2019-is-still-incapable-of-properly-importing-reviewed-bilingual-files-but-is-this-a-feature

...which, as it turned out, was actually a "feature" and not a bug?

SDL has a long history of making life difficult for their customers.

OK, but having to look for, download and install plug-ins that often break Trados, and then force us to look for help through remote sessions is not the ideal approach, is it? And how about having to download individual plug-ins (if they even exist) for each of the initially unsupported formats?

Paul said:

How about this:

https://appstore.sdl.com/language/app/file-type-definition-for-wordfast-txml/247/

This solved the problem, thank you! I had to recreate the project and pre-translate the file again. The only problem I ran into is a tag discrepancy that forced me to manually insert tags for 30% of the translated content.

Thank you again for your help!

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.

Pavel Tsvetkov said:

OK, but having to look, download and install plug-ins that often break Trados, and then force us to look for help through remote sessions is not the ideal approach, is it?

It is. Most user will not need the plug-ins. And the plug-ins are available directly from Studio. If you need something extra, then go to add-ins and search for that.

Bloating the app will all bells & whistles which could probably be used by the vast majority of 0,000001% of all users would just lead to more problems and even more moaning here. It is much better to let the people install what they need extra.

Paul said:

What other formats do we refuse to recognize?  I can't actually think of any that I cannot handle in Trados.

jpeg... But don't take it earnestly. Certainly there will be a format here and there, which is not yet simply recognized. But for many formats it is simply possible to create your own file type.