search

WeblateOrg / weblate

Web based localization tool with tight version control integration.
https://weblate.org/
GNU General Public License v3.0
4.5k stars 993 forks source link

Allow user to configure automatic suggestion services #9689

Open yilmazdurmaz opened 1 year ago

yilmazdurmaz commented 1 year ago

Describe the problem

For the last few days, "hosted" weblate has been lacking suggestions from all translator sites (except LibreTranslate).

I would say the admin has disabled them, but this could, very well, be the exhaustion of monthly free usage.

Whatever the reason, it definitely slows down me for the thousand-strings project I am working on.

Describe the solution you'd like

You can never know what may happen to the weblate version ("hosted" or custom) and the suggestions.

They are definitely great tools to ease the pain of especially the writing, and provide speed to the users.

This feature should not be a responsibility of Weblate instance, and must be "shareable" to users at will.

So, I would like to have a way to use my own API keys for those sites (whether free or paid) in such a situation.

Describe alternatives you've considered

The alternative is to copy-paste strings into a translator site and then copy-paste the result back into Weblate. It is too much tiresome.

Screenshots

No response

Additional context

No response

nijel commented 1 year ago

Projects can configure own keys for machine translation services.

yilmazdurmaz commented 1 year ago

Projects can configure own keys for machine translation services.

But that still can be an issue if they use free API keys and their monthly usage depletes. Especially since there will be lots of languages (and users) to use them.

If we can have user-level access to these services, each user can use their own API keys and may have unlimited suggestions if they pay for those services.

nijel commented 1 year ago

It might make sense in some cases, but it is not realistic to expect every translator to configure this. So it is IMHO better to configure this at the project level, so that more translators can utilize services which the project considers useful and legitimate to use.

github-actions[bot] commented 1 year ago

This issue has been put aside. It is currently unclear if it will ever be implemented as it seems to cover too narrow of a use case or doesn't seem to fit into Weblate.

Please try to clarify the use case or consider proposing something more generic to make it useful to more users.

yilmazdurmaz commented 1 year ago

but it is not realistic to expect every translator to configure this

I think you mistook it a bit. The usual project-level setting will continue to exist.

It is also not for wandering translators either. Those are mostly around 20-30 strings, then vanishes

What I tried to describe is "to add" to it., so that long-term users may use their own keys if they "need" it (and will surely need it).

Right now, Godot Engine project lacks suggestions and this feature would greatly help us, translators of this project (~50k strings)

https://hosted.weblate.org/projects/godot-engine/

one thing to note is that it is not urgent right now, but would be an essential feature of Weblate.

nijel commented 1 year ago

If Godot wants to use machine translation, the project admins should configure it.

User configuration indeed makes sense, but it is a feature that a few users will use and thus doesn't have a priority.

yilmazdurmaz commented 1 year ago

If Godot wants to use machine translation, the project admins should configure it.

As I stated before, it is not if they prefer or not, but rather if they use free API keys or not. I was using the suggestions from 4-5 services last month, and now there is only 1 left working. (server or project level problem? I don't know)

So it is safe to say Godot is set to use these services but it seems to work with free API keys (natural for an open-source free software).

By the way, It seems you don't feel good against machine translations. I do too as they are about 60-90% accurate, but they are evolving faster. Plus, a bit of real-person touch is what makes them very useful here in Weblate: I have to type less to complete a 50-word string.

Anyways, as I said, it is not urgent but would be an essential part.

nijel commented 1 year ago

There used to be a site-wide configuration at Hosted Weblate, but it is now gone for several reasons. So the project has to configure own if it is desired to use machine translation.