Hi,

at the moment we don't have such API available for public use. It is on our backlog and I do believe it will be available relatively soon as you are not the only customer with request for such API.

Please keep looking into this forum as we will be announcing when the new APIs will be available for testing.

Regards

Patrik

OK, good to know. Thanks a lot for the quick reply, Patrik.

We were faced with the same issue and are considering to just build a one-way sync interface. E.g. have a process that updates/creates normal Multiterm files. It's not perfect, but would also make it easier with external translators, as you can just send them a normal package. If you're interested, let me know. Maybe we can work together.

Thanks  a lot, Remy. It would be a workaround, but that would mean that the translator needs to create or assign a MultiTerm memory for each project, right?

This is a very interesting topic, and we have raised it with SDL previously - the ability to be able to interface Trados with external terminology providers (e.g. in a similar way a plugin for an external translation provider such as machine translation can be created).

Unfortunately, at the time this was not available and it would be great to see such an API in the near future!

We have automated exports of terminology into termbases on a regular basis, which are then shared with internal and external translators. The issue with this is that it can become time intensive (e.g. recreating a termbase with 100.000 entries can take several hours), and when syncing existing termbases search indexes for Trados sometimes seem to be not updated.

Also, the main benefit of using an external terminology provider instead of distributing exports for us would be that all clients can use up to date terminology at all times. Previously, I was under the impression that this could already be done from a technical point of view - similar to how a trados client communicates with a Multiterm server - but this obviously is not documented or there are some technical obstacles I'm not aware of.

In any case, please keep us updated on any development in this regard!

Hi Patrik,

Since there are quite a few SDK users who are interested in this feature, could you perhaps give an indication of the priority in the backlog? Maybe you already have it assigned to a specific sprint. If the feature is coming some time soon, I'd rather wait for than investe time and effort in building the functionality based on the TranslationProvider API.

Thanks a lot.

Cheers,

Martin

@ mwunderlich Yes, they would have to create or assign a MultiTerm db to every project. But you can just put that into your Project Template and that's it.

@ mwunderlich Yes, they would have to create or assign a MultiTerm db to every project. But you can just put that into your Project Template and that's it.