-
-
Notifications
You must be signed in to change notification settings - Fork 958
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
Prevent translators to go to next string after saving current #5047
Comments
This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger. In case your question is already answered, making a donation is the right way to say thank you! |
It's currently not possible. Can you please clarify the use case a bit? Are they translating into more languages simultaneously? |
Yes sure, some guys can translate 2 or 3 languages, and some guys just move external resources into weblate. |
Or sometimes the content are the same, just need to copy and rewrite to every language. |
Would be nice if users could mid-click the "Save" in the regular editor, although that would open new tabs. |
This can be a workaround. 👍 |
I don't think it's possible to do a POST request while opening a new browser window. Having another button to save and stay on current unit is probably best approach here. |
I agreed have another button 👍 |
How bad of an idea is it to save what is in the field when the tab closes (provided no other changes of the string happened meanwhile)? |
Hello. I'd just like to upvote this request, it would be immensely useful for us. |
👍 |
Thank you for your report; the issue you have reported has just been fixed.
|
Describe the issue
How to prevent translators go to next string after saving current...
Is there a setting to disable it? As some users told me they always need to go back then they can go to another language and update it, it's waste of time.
The text was updated successfully, but these errors were encountered: