-
-
Notifications
You must be signed in to change notification settings - Fork 969
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automatic translation support adding translation as "approved" #9048
Comments
The strings should be added as “for review” right now. I thought you wanted to have the possibility to add strings as “approved”. |
This issue has been added to the backlog. It is not scheduled on the Weblate roadmap, but it eventually might be implemented. In case you need this feature soon, please consider helping or push it by funding the development. |
I just tried tool Automatic translation. There the Automatic translation mode Add as translation (together with Enabled reviews Setting) sets strings as for review. So it this is the same at the addon Automatic translation, then this ticket is unnecessary. Just that because of the bug #8979 I could not see it. |
I still think it makes sense to add an option to add string as approved, so let's keep this issue open. |
To implement this:
|
This issue seems to be a good fit for newbie contributors. You are welcome to contribute to Weblate! Don't hesitate to ask any questions you would have while implementing this. You can learn about how to get started in our contributors documentation. |
is this issue closed ? |
No, it is open. |
Thank you for your report; the issue you have reported has just been fixed.
|
Describe the problem
Following ticket #8979, I would like to have an option to set the automatically translated strings as "for review". This will correspond with the "for review" workflow.
Describe the solution you'd like
Add an option "Add as for review" to Automatic translation mode of the add-on set-up.
Describe alternatives you've considered
No response
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: