Update Russian localization #1036

New Issue

MrUnknownDE · 2026-04-05T16:43:29+02:00

MrUnknownDE commented

2026-04-05 16:43:29 +02:00

Originally created by @Felix14-v2 on 1/18/2026

Summary

Massive rework and updating of the Russian localization. The main goal is to create a clear, easy-to-read and consistent localization. A collaborative work of @AndylgTom and me (huge thanks to him for reviewing the changes!).

The main issues that this rework tries to solve

The current translation is a mess. Not only because the machine translation (obviously someone used a translator in the past) was generated without an understanding of local terms or the entire 3D-printing industry, but also because, in most cases, you can't just translate word-by-word into Russian. Compared to the English language, in Russian, theme and rhyme are conveyed by the word order in the sentence. Word-by-word translation is understandable, but it is difficult to read, and it is always better to gracefully reorder the words based on the context to provide the information in the most effective manner.
A lot of translations are too long to fit in the allotted space. The main issue here is with the print settings sidebar: the length of the tab names forces users to either expand the sidebar and reduce the workspace, or perform multiple clicks in order to navigate (for example, from the "quality" tab to the "others" tab and vice versa).
There's no glossary in the localization. A single term can be translated differently in different places, and this inconsistency sometimes leads to a huge misunderstanding.

Summary of the main changes

I started creating a glossary and Russian localization guidelines for future translators (WIP)
Most of the inconsistent translations have been fixed
Added new translations for the main UI
Added translation of the entire Bambu filament database
Fixed some small issues in the web-based windows (text.js)

Remaining issues

There are still many places with broken encoding, leading to the inability to see translated text. All known places are tracked in this table.
Not all strings are translatable (should I create a separate issue with them?).
The current approach to handling localization has a massive drawback: a string with a single term, that must be translated differently based on context, can be used multiple times and can not be changed based on context. This leads to huge problems with handling connections between words (especially in sentences, constructed using common placeholders). Andy created an issue (#6970) with an example of such a problem, but it was closed due to inactivity and has never been solved.
I don't own a Bambu 3D printer. I don't translate strings which I can't verify in the UI or by reading the code, so some Bambu-related and some new H2D-related strings are still untranslated/unchanged.

Additional

I'm still not sure where and how best to store the glossary and guidelines, should I use the Poedit comment system for that? I personally use an IDE to work directly with Git and search through the code and translation history, and I don't understand well how to make an integration with Poedit.
I'm still adding translations for new features and will mark the PR as ready when I'm done.
Also the 3rd issue is unsolvable on my side. I use workarounds to hide the problem whenever possible, but to solve it, the entire localization system must be redesigned. Please let me know if you have any suggestions or questions.

*Originally created by @Felix14-v2 on 1/18/2026* ## Summary Massive rework and updating of the Russian localization. The main goal is to create a clear, easy-to-read and consistent localization. A collaborative work of @AndylgTom and me (huge thanks to him for reviewing the changes!). ## The main issues that this rework tries to solve - The current translation is a mess. Not only because the machine translation (obviously someone used a translator in the past) was generated without an understanding of local terms or the entire 3D-printing industry, but also because, in most cases, you can't just translate word-by-word into Russian. Compared to the English language, in Russian, theme and rhyme are conveyed by the word order in the sentence. Word-by-word translation is understandable, but it is difficult to read, and it is always better to gracefully reorder the words based on the context to provide the information in the most effective manner. - A lot of translations are too long to fit in the allotted space. The main issue here is with the print settings sidebar: the length of the tab names forces users to either expand the sidebar and reduce the workspace, or perform multiple clicks in order to navigate (for example, from the "quality" tab to the "others" tab and vice versa). - There's no glossary in the localization. A single term can be translated differently in different places, and this inconsistency sometimes leads to a huge misunderstanding. ## Summary of the main changes - I started creating a glossary and Russian localization guidelines for future translators (WIP) - Most of the inconsistent translations have been fixed - Added new translations for the main UI - Added translation of the entire Bambu filament database - Fixed some small issues in the web-based windows (text.js) ## Remaining issues 1. There are still many places with broken encoding, leading to the inability to see translated text. All known places are tracked in [this table](https://github.com/OrcaSlicer/OrcaSlicer/issues/4042#issuecomment-3289655315). 2. Not all strings are translatable (should I create a separate issue with them?). 3. The current approach to handling localization has a massive drawback: a string with a single term, that must be translated differently based on context, can be used multiple times and can not be changed based on context. This leads to huge problems with handling connections between words (especially in sentences, constructed using common placeholders). Andy created an issue (#6970) with an example of such a problem, but it was closed due to inactivity and has never been solved. 4. I don't own a Bambu 3D printer. I don't translate strings which I can't verify in the UI or by reading the code, so some Bambu-related and some new H2D-related strings are still untranslated/unchanged. ## Additional I'm still not sure where and how best to store the glossary and guidelines, should I use the Poedit comment system for that? I personally use an IDE to work directly with Git and search through the code and translation history, and I don't understand well how to make an integration with Poedit. I'm still adding translations for new features and will mark the PR as ready when I'm done. Also the 3rd issue is unsolvable on my side. I use workarounds to hide the problem whenever possible, but to solve it, the entire localization system must be redesigned. Please let me know if you have any suggestions or questions.

MrUnknownDE closed this issue

2026-04-05 16:43:29 +02:00

Sign in to join this conversation.

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/OrcaSlicer#1036