Vilius Butiskis

http://multifarious.filkin.com

I am sorry, but I don't find this resource helpful as it does not mention TMX not once

Vilius Butiskis

it certainly does. If you can’t see it then I’ll elaborate when I get back in.

Unless we aren't talking about the main article in the link which lists new features of Studio 2021.

Vilius Butiskis

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.

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.

Vilius Butiskis said:

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

Vilius Butiskis said:

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

Hi Alison,

In my view you are only thinking from a translator point of view. This is, a receive a new project, in one language, with one TM in TMX format and it just takes a few minutes to create a .SDLTM and import the TMX file. Ok fine.

First of all I would like to say that a TMX is NOT an old decrepated format BUT The Translation Memory eXchange standard format. This is an XML specification for the exchange of translation memory data between computer-aided translation and localization tools. Nowadays most if not all CAT/Localization tools use this format, so it allows to exchange TMs between them.

Now try to think from a LSP perspective. I am the one preparing the projects. I work with a new client and I receive dozens or hundreds of TMs in TMX format that I have to convert to .SDLTM (different specialities 25-30 languages). I receive tons of different translation projects where the client uses CMS/Tools that export the translations memories in the standard TMX on daily basis. It’s a huge waste of time creating .sdltm one by one file and importing the TMXs.

It’s not only a problem to open the TMX. We cannot Upgrade the TMXs to .SDLTM in batch mode and we can’t import the TMX format when creating a new project (In 2019 studio allow to upgrade the TMXs when creating a new project)...

I understand that SDL removes Google translator. They want to sell their platform “Be global”. But the TMX format???

Regards,

Felipe

Felipe Gonzalez Lopez

Felipe Gonzalez Lopez said:

I understand that SDL removes Google translator. They want to sell their platform “Be global”. But the TMX format???

Actually you're wrong on both counts.

We removed Google translator because it's no different to any other plugin on the apptore.  To be honest I've argued against that being in the product for years so I'm glad we finally removed it.  It has nothing to do with wanting to sell our own platform... in fact we offer it for free for all users up to a point (enough for freelancers never to have to pay at all) compared to Google who do not.  So now you access Google MT via the MT Enhanced plugin which we will work on to improve further as it was originally developed by a 3rd party developer many years ago and badly needs an overhaul.

The TMX format... it was accessible because it was part of the "Upgrade TM" routines so when this was removed and made part of a plugin it also went.  The unfortunate part is that when the development team completed the plugin the omission of the TMX quick upgrade was an oversight.  Try to imagine just how much was going on when all this happened... and it was missed.  Wasn't even picked up in Beta testing with real users.  It will come back.

So I think we can drop this particular part of the discussion as I'd already said we'll put it back in the verified response to this thread.

Thank you Paul

I knew you would answer this post better than I could.

Ali