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/.../

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?

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.

Jerzy Czopik said:

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

Agreed, but that argument does not apply to the functionality of being able to open source formats. And especially the source formats created by Déjà vu X, MemoQ and Wordfast. Recognizing and opening those formats created by the three other popular CAT tools can and should be included in the vanilla version of Trados that customers buy. What would be the argument not to do so, but to allow it through a plug-in that most customers do not even know exists? And how about having to download individual plug-ins (if they even exist) for each of the initially unsupported formats? It is mind-boggling.

Jerzy Czopik said:

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

Agreed, but that argument does not apply to the functionality of being able to open source formats. And especially the source formats created by Déjà vu X, MemoQ and Wordfast. Recognizing and opening those formats created by the three other popular CAT tools can and should be included in the vanilla version of Trados that customers buy. What would be the argument not to do so, but to allow it through a plug-in that most customers do not even know exists? And how about having to download individual plug-ins (if they even exist) for each of the initially unsupported formats? It is mind-boggling.

Pavel Tsvetkov said:

Recognizing and opening those formats created by the three other popular CAT tools can and should be included in the vanilla version

Why? CAT hopping is not plain vanilla function. It requires much more than just open and translate a file format. Requesting this in the basic functionality exceeds the needs of I would say 95% of users of the software. And for good reason: allowing everyone to go for CAT hopping is asking for big trouble and no project manager in the world will be keen on that.

Dzień Dobry, Jerzy Czopik

I fully agree with your excellent point here, I only hope that every reader thought of "translating" your "-hoping" into "-hopping".

Knowing you, I am sure there won't be any hard feeling. Best regards.

Dear Gérard

Many thanks, I already modified my hopeless mistake and hope you can forgive me my hopping over words...