Translate
After upgrading to Studio 2021 I've noticed that I no longer have an option to select type of TM file in Translation Memories -> Open -> Dialog box file type dropdown box. So my question is how do I do it now?
After upgrading to Studio 2021 I've noticed that I no longer have an option to select type of TM file in Translation Memories -> Open -> Dialog box file type dropdown box. So my question is how do I do it now?
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
I am sorry, but I don't find this resource helpful as it does not mention TMX not once
it certainly does. If you can’t see it then I’ll elaborate when I get back in.
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
Unless we aren't talking about the main article in the link which lists new features of Studio 2021.
you probably need to refresh... that’s not the home article. You need this one:
https://multifarious.filkin.com/2020/08/15/some-you-win-some-you-lose/
I published it yesterday.
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
Thank you, this has answered my question. Sad, it looks like a step back. I was hoping way advanced tools to manage TMs implemented in the future releases, but it looks like Trados is choosing a path where the app is becoming more and more a client app like many other CATs.
Sad, it looks like a step back.
Hi there,
It is a step back in order to be able to take a different, more effective step forwards. My appraisal of the article is that certain functional access was based on 'old code' and had to be removed to improve speed and efficiency, but would most likely be re-added based on end user requirements, based on new, faster code.
In the article Paul gives several possible ways to open TMX files in Studio. I use the method he described last... if I receive a tmx, I always create a new memory based on the client's previous TM (so that I have any customisation instantly available) then I import the TMX into that. It's clean and quick and I can name it according to the date I received it and its context. It has the extra advantage of being the latest version so no need to upgrade. I much prefer that to adding it to an existing TM.
I'm pleased that old code-based stuff has finally been eliminated.
All the best,
Ali 
Sad, it looks like a step back.
I'd agree with you... but I'm pretty sure it's temporary and we will do something to address this in a future release without keeping the old code which was the priority for now.
it looks like Trados is choosing a path where the app is becoming more and more a client app like many other CATs.
You could not be more wrong. We removed this to get rid of old code. In terms of what we have done we are maintaining Studio as a desktop application AND making it possible to work in the cloud by synchronising them both. I don't think any other CAT tool does this to the extent we have now and we will improve. Becoming an app that always requires a cloud connection is not an objective. Synchronising the two is an objective.
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
If returning functionality from the older version to a newer one is on the roadmap that is fine even if no new functionality for managing TMs is planned (though I have expected that). For example such trivial tasks as removing formatting tags from old TM entries without updating entry dates; extracting groups of high similarity TM entries to delete wrong ones – there were 7 iterations of Trados Studio and I still must rely on 3rd party tools or my programmed tools.
It is a relief there are other solutions (including running Studio 2019 alongside) for now. But are there any obligations for devs of those add-ons to maintain compatibility with all future updates of Studio 2021 for which I have purchased the license?
If returning functionality from the older version to a newer one is on the roadmap that is fine even if no new functionality for managing TMs is planned (though I have expected that). For example such trivial tasks as removing formatting tags from old TM entries without updating entry dates; extracting groups of high similarity TM entries to delete wrong ones – there were 7 iterations of Trados Studio and I still must rely on 3rd party tools or my programmed tools.
It is a relief there are other solutions (including running Studio 2019 alongside) for now. But are there any obligations for devs of those add-ons to maintain compatibility with all future updates of Studio 2021 for which I have purchased the license?
But are there any obligations for devs of those add-ons to maintain compatibility with all future updates of Studio 2021 for which I have purchased the license?
No. I don't even know what applications you're referring to either.
There aren't even obligations on SDL to keep providing the features you have today. It's unlikely we'd remove things that people use and need, but there are no obligations.
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
I was referring to add-ons that can be used as substitutes for removed functionality.
Thanks for explaining the company's attitude, I have nothing else to add.
Thanks for explaining the company's attitude
This has nothing to do with the company's attitude. This is the reality of all software development the world over. Nobody has an obligation to continue to maintain compatibility. If it makes sense on the whole then most will do it... nobody has to.
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
When one buys Windows or any other peace of software there is usually a timeframe indicated until when it will be fully maintained and improved, then security maintained and finally deprecated. In this case it sounded really harsh, like we may remove features at will, may discontinue development at any moment and you should not have any expectations as a buyer. Further more feature removal was not mentioned for those who placed pre-release orders.
When one buys Windows or any other peace of software there is usually a timeframe indicated until when it will be fully maintained and improved, then security maintained and finally deprecated.
As there is here too... but that does not preclude any software developer from changing the way things are delivered or even if they are included at all during this period. It's simply not possible to promise things like this so I answered your direct question.
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
We have deviated from the topic a lot :) thank you for your help with TMX files
Perhaps if I had known, I would not have upgraded. It is commercial bad faith not to inform you of the features they are going to remove when they offer you an upgrade.
it’s a freely available plugin to put it back. It’s also in the release notes on the KB. It’s also in the help ribbon to make it even easier for users to find.
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