#1612 Clarify requirements for DeepL API key

[Jean-Christophe Helary]

https://www.deepl.com/pro#developer

So the interface that we have to connect to the API is confusing and useless. We need to remove it.

As of March 2022, only the "Advanced" and above plans support use with CAT tools. We should note this in the connector GUI.

[Aaron Madlon-Kay]

This has been the case for years. API keys that were created before a certain point can still use their API v1, which is why we have kept the MT connector.

[Jean-Christophe Helary]

On Feb 4, 2022, at 10:21, Aaron Madlon-Kay amake@users.sourceforge.net wrote:

This has been the case for years. API keys that were created before a certain point can still use their API v1, which is why we have kept the MT connector.

Thank you. So I guess it's a UI/documentation bug. Would adding "v1" somewhere in the string be acceptable ?

--
Jean-Christophe Helary @brandelune
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/

[Aaron Madlon-Kay]

Unless things have changed I think you can still get v1 keys, but they don't work for API access. So just saying "v1" isn't enough; only people with old-enough v1 keys can use it.

Someone™ should figure out the current state of affairs:

• Can you still get v1 keys?
• Are "old" v1 keys still able to access the API?
• What exactly was the cutoff date?

If old v1 keys still work and we can determine the cutoff date, then we can give meaningful guidance to users. If old v1 keys can no longer use the API then we should just remove the connector entirely.

[Aaron Madlon-Kay]

Unless you have new information that something has changed such that even the older keys are not usable?

[Aaron Madlon-Kay]

We have anecdotal confirmation from a user that they have a DeepL API key that works as of March 2022. So we will not be removing the connector.

It seems that either the "Advanced" or "Ultimate" plans are required. Indeed, their plan comparison notes that "CAT tool integration" is included with "Advanced" and above.

So it would be useful to note that in the UI.

[Aaron Madlon-Kay]

Ticket moved from /p/omegat/bugs/1087/

[Aaron Madlon-Kay]

Ticket moved from /p/omegat-plugins/feature-requests/9/

[Jean-Christophe Helary]

Thank you Aaron for the update.

[Hiroshi Miura]

I think that DeepL connector is for translators who live in limited places and who has an account.
It should be a plugin provided by outside of OmegaT distribution, because not all user can use it.

Same can be said for all the MT connectors, except for one that can be used WITHOUT account registration.

[Jean-Christophe Helary]

I would tend to agree with that in principle. But we have the option offered now and I don't see a rationale to remove the interface we have now (unlike with TaaS where the service does not work anymore).

So, what about we think of "externalize" the function to a plugin in a later version ?

[Hiroshi Miura]

So, what about we think of "externalize" the function to a plugin in a later version ?

A plugin management on OmegaT is too difficult for computer newbies.
It is a reason why users are not favor of externalized plugins.

I've proposed several improvements for plugin management, that help users to install plugin easily.

https://github.com/omegat-org/omegat/pull/109

When installation and uninstall are easy enough, many additional features can be externalized.

[Jean-Christophe Helary]

It seems to me that it is now fixed in the manual.

@miurahr9 do you want to rename the RFE so that it fits your plugin related developments, or should we register them in a different RFE?