translate: complete missing ru_RU backend strings (django.po) - #25518
Open
pagbest154-cmd wants to merge 1 commit into
Open
translate: complete missing ru_RU backend strings (django.po)#25518pagbest154-cmd wants to merge 1 commit into
pagbest154-cmd wants to merge 1 commit into
Conversation
Update locale ru_RU 08.2026 Signed-off-by: FerrumNST <pagbest154@gmail.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #25518 +/- ##
==========================================
- Coverage 91.67% 91.63% -0.04%
==========================================
Files 1151 1151
Lines 73416 73416
Branches 4054 4054
==========================================
- Hits 67301 67275 -26
- Misses 6073 6099 +26
Partials 42 42
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Details
What does this PR change?
locale/ru_RU/LC_MESSAGES/django.powith Russian translations for previously untranslated backend strings (~412msgidentries).Last-Translator/PO-Revision-Date(2026-08-27).%(username)s,{minutes}, OAuth/SAML/LDAP names) are preserved.Note: This PR updates backend locale only. Frontend
web/xliff/ru_RU.xlfis not included in this change.Why is this change needed?
Russian (
ru_RU) backend locale in upstream still had a large set of emptymsgstrentries for recently added strings. Completing them improves Russian UI/API messages for administrators and end users without waiting for Transifex sync.How was this tested?
django.po.locale/ru_RU/LC_MESSAGES/django.pofrommain— only missingmsgstrvalues were filled; existing translations were not overwritten.make core-i18n-compileor Djangocompilemessagesforru_RU— no PO syntax errors.Linked issues
N/A — community locale improvement.
AI disclosure (required by AI_POLICY.md)
AI assistance (Cursor/LLM) was used to draft and review Russian translations for bulk missing strings. All entries were manually reviewed for terminology consistency with existing
ru_RUstrings (e.g. «Провайдер», «Сопоставление свойств», «Этап», «Источник») before submission. I can explain the changes and rationale without relying on AI.Checklist
make all) — for locale-only PR often skipped by contributors; if maintainers ask, run at least PO compile / minimal checkmake docs) — not applicable