-
-
Notifications
You must be signed in to change notification settings - Fork 168
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
Release notes translation #549
Comments
I ended up using Google Translate. If you or other translators see an error in the automatic translation, please submit a PR editing this file (e.g. 'metadata/$localeCode/changelogs/$newestVersion.txt' |
Good choice! I completely forgot about what my work colleague said some time ago. For short texts Google translate works better than Deepl. |
I looked on current translations and saw they are pretty good. I think there is no need to fix anything (at least for now, we'll see how it will be going for future release notes). I'm glad to see it works well. |
That's good to hear :) |
This issue comes from discussion with @adil192 for commit 96a6119.
Since this commit, Saber shows release notes to all users (includes users with Czech or other language set). They see English release notes but they don't understand them (when don't speak English too much or at all). Manual translating isn't the best idea (as @adil192 noted in referenced discussion) because it slows down updating process. So, what about using automated machine translation for these messages? Nowadays machine translation using language models is pretty good, so for release notes it should be good enough. I have Deepl on mind, e.g.
The text was updated successfully, but these errors were encountered: