Hi to SDL developers/programmers/PMs and to all,

in these last weeks, after the release of SDL 2017 SR1 and CU6 we have seen several complaints regarding the overall SW performance, and we have read various useful answers/solutions to solve these issues (namely, deactivating LookAhead, Fragment Matches or other options).

Among others, in a recent post, Damián Santilli expressed a thought that I completely share with him:

“[…] I fear that the company is paying so much attention to machine translation and other things that they're doing things the wrong way for the users that love this tool for the everyday tasks that a freelance translator has to undertake. […]”

Now I have a proposal, if at SDL deem it practicable and not just a “dream”.

Actually, we have several editions of the commercial SW, with different activated modules/options and different selling price grids:

• SDL Trados Studio 2017 Starter
• SDL Trados Studio 2017 Freelance
• SDL Trados Studio 2017 Freelance Plus
• SDL Trados Studio 2017 Professional

Taking into consideration that not all SDL Studio freelance translators do not (o do not want) access to the various “cloud” or “MT” features directly from SDL Studio, what about creating two more editions, e.g.:

• SDL Trados Studio 2017 Freelance/Freelance Plus without the activation of modules/features to access the “cloud” or “MT” engines/features
• SDL Trados Studio 2017 Freelance/Freelance Plus with the activation of modules/features to access the “cloud” or “MT” engines/features

In fact, these proposed editions will be something similar to the SDL Studio Professional and SDL Studio Freelance/Freelance Plus where, in the latter one, if I am not in error, the difference is tied to the unavailability of some modules/features (e.g. just 5 languages, creation on Project Packages, etc.).

Obviously, these two new proposed editions should have a proper selling price grid.

Should this proposal, if and when deemed feasible, solve performance issues pointed out by a number of SDL Studio users not using “cloud” or “MT” features?

Just to give an example, when we decide to buy a car (or any other product) we hold in due consideration its performances/options/functions, and after having analysed them we opt for a top range Volvo/Lexus/Mercedes/BMW/etc. model or a medium/low range one. Ideally, we do not buy a top range product with extraordinary options/features/accessories we will never want or use, so we will tend towards a model which meets our requirements avoiding “not requested” features/functions/options.

Is this anything that SDL could take into consideration?

Thank you.

Claudio