Only the automatic translation uses the current selected translation module, the rest uses Google

[GruiaChiscop]

When Switching to another translation module, e.g. deepl, only the auto translation uses it, but if I want only to translate the last spoken word or just the clipboard, it uses Google as the translation module. Shouldn't this apply to the all features?

[hxebolax]

Hello, no.
Simultaneous translation is the only feature that works across different modules.
Other functions, such as translating focused text, translating from the clipboard, etc., are done through Google Translate.
It is the only translator I can confidently rely on to provide translations at any time.
The other modules can be added, but at some point, they might stop working. For example, if we use Microsoft's and try to translate a long selected text, it would not be possible as we would hit a quota error.
That's why I decided to stick with Google Translate for the other functions.
Best regards.

[zersiax]

Google is unfortunately inferior for some languages and hardcoding it to use this is actually preventing me from using the addon as is. I get that reliability is important but you already have several modules to pick from, if one were to go down the user can just switch to another one. Right now, the user doesn't have that option.
I'd therefore second the feature request to please add this, it'd make the addon far more useful for a huge lot of applications.
Failing that, how can I modify it myself so it actually uses the API I want to be using?
I changed the call to translate_google_api_free in the managers_translations.py file but that doesn't seem to be enough. Do I need to comment out that if statement above it to make this work?

[hxebolax]

Hello, I'm sorry.
But if things are done, they are done for a reason.
Modifying what is being requested would be detrimental because, for the other APIs, the extraction method is more difficult and less allowed by the services.
If I did what is being requested here, in two days we would be left without services—for example, in DeepL Free—since it would lead to blocking the requests.
The most permissive API is Google's, which is why it is the default for secondary actions, and at least officially, I am not going to change it because if I did, we would soon be left with nothing.
Best regards.

[zersiax]

This concern seems exceedingly unlikely given everyone uses their own API key, which in DeepL-free's case allows for 500000 characters a month. That is a lot of text.
If this wasn't the case, and everyone'd be using your API key, or a small pool of keys, I could see this having some merit but as things stand now it just doesn't. If you're worried about this you could always just limit the options for module selection to paid offerings, that way, the API providers will just be getting business and likely won't cause any trouble. Not telling you how to write your addon, of course, but as things stand I feel you have the potential t be a lot better/more appicable than, say, instantTranslate, but are held back by the fact that almost everything uses Google