Thanks for the feedback. We appreciate that you list specific examples where the quality is lacking. That’s actionable feedback we can give to the translator.
Also, there’s no need to list untranslated strings, all of them will be done eventually. It’s a lot of work and just moments ago I merged another batch of translations which should add many of the missing translations.
A lot of work has been done and many of the shortcomings have been corrected - this is on the one hand. On the other hand, many of the changes made are not yet satisfactory.
If I commented on the translation of all disputed lines, then there would be a lot of comments.
Therefore, let me pay attention of translators to a number of general issues.
I hope these comments will affect the quality of the new translation.
I’m sorry that I’m writing in Russian, but it’s so much easier for me and I would like to forward this message to the translation team.
The list is far from complete, perhaps colleagues from the forum will be able to supplement this list:
Probably the most controversial part of this description. Many terms have been used within this forum for a long time, and they have every right to exist, such as Sympathies, instead of the overused likes (this was not my translation, but I didn’t touch it, it seemed quite “cozy” to me). Some terms are quite established not only on this forum, but also on other resources of the Runet, and the replacement of some of them looks strange in places:
Post → Сообщение (The proposed term запись (recordset) is usually used in the context of databases.
(private) message, PM → личное сообщение, also known as “ЛС”. Example: “Написать в личку” - has long been an established phrase. The proposed term “сообщение” will only confuse the user, as it is usually associated with “regular posts”.
These are just a few examples, there are many more such terms, some of which have already been mentioned by @hiddenseal.
It would be nice to use a unified glossary of terms, many of the terms that have been changed have only been changed in part of the files. Example: журналы, категории (although, who was bothered by “РАЗДЕЛЫ форума”, this is again related to the question above about established phrases in the Runet space: is it worth changing a spade for a poker for exact correspondence to the original term?)
Such translation is encountered repeatedly, here are just a few examples:
enable: "Включить чат"
flag: "Флаг"
emoji: "Вставить эмодзи"
For flag - Pay attention to the neighboring verbs (Вставить/Включить), in this context it is more logical to use the verb Пожаловаться (Complain).
content: "Ответы на вопросы"
FAQ – in this context, it is Правила (Rules). Yes, the direct translation is Answers to questions, but if you open the section and pay attention to the content of the message, it is precisely the RULES of the forum, without a single question.
new_topic: "После утверждения этого элемента появится новая тема"
Yes, the original uses “item”, but how can you approve an item? This always refers to the moderation of a message, for example: “After approving this message, a new topic will appear.”
Errors still remain, and in a significant number.
sidebar:
unread_count:
one: "%{count} непрочитанная"
few: "%{count} непрочитанные"
many: "%{count} непрочитанных"
other: "%{count} непрочитанной"
manage:
one: "Управление резервными кодами. У вас остался <strong>%{count}</strong> резервный код."
few: "Управление резервными кодами. У вас осталось <strong>%{count}</strong> резервных кода."
many: "Управление резервными кодами. У вас осталось <strong>%{count}</strong> резервных кодов."
other: "Управление резервными кодами. У вас осталось <strong>%{count}</strong> резервного кода."
reached_hour_MF: |
<b>{relativeAge}</b> – <a href='{url}' target='_blank'>{rate, plural, one {# ошибка в час} few {# ошибки в час} many {# ошибок в час} other {# ошибки в час}}</a>: достигнут предел для настроек сайта — {limit, plural, one {# ошибка в час} few {# ошибки в час} many {# ошибок в час} other {# ошибки в час}}.
reached_minute_MF: |
<b>{relativeAge}</b> – <a href='{url}' target='_blank'>{rate, plural, one {# ошибка в минуту} few {# ошибки в минуту} many {# ошибок в минуту} other {# ошибки в минуту}}</a>: достигнут предел для настроек сайта — {limit, plural, one {# ошибка в минуту} few {# ошибки в минуту} many {# ошибок в минуту} other {# ошибки в минуту}}.
exceeded_hour_MF: |
<b>{relativeAge}</b> – <a href='{url}' target='_blank'>{rate, plural, one {# ошибка в час} few {# ошибки в час} many {# ошибок в час} other {# ошибки в час}}</a>: превышен предел для настроек сайта — {limit, plural, one {# ошибка в час} few {# ошибки в час} many {# ошибок в час} other {# ошибки в час}}.
exceeded_minute_MF: |
<b>{relativeAge}</b> – <a href='{url}' target='_blank'>{rate, plural, one {# ошибка в минуту} few {# ошибки в минуту} many {# ошибок в минуту} other {# ошибки в минуту}}</a>: превышен предел для настроек сайта — {limit, plural, one {# ошибка в минуту} few {# ошибки в минуту} many {# ошибок в минуту} other {# ошибки в минуту}}.
Since Russian terms are not the most compact, the length of lines in translation has noticeably increased in places, which has affected the correct display of some inscriptions on buttons and in text fields, the size of which is limited. Example:
Admin-> Администрирование
Even on regular monitors, the inscription does not fit on the button, let alone on gadgets with a minimum screen diagonal, where this button takes up significant space. Yes, the short term Админка (Admin panel) is slang, but it is understandable to everyone and fits correctly into the interface.
Hyperlinks and example addresses are usually left “AS IS”:
from_placeholder: "sender@example.com"
to_placeholder: "recipient@example.com"
cc_placeholder: "copy@example.com"
...
payload_url_placeholder: "https://example.com/postreceive"
I believe that in the new translation, automatic yo-fication was performed at the very beginning of the translation process, since now (probably after manual text editing) the letter Ё is missing in many places (её, ещё..).
Previously, I did not distract developers with such minor issues, but when working with the forum, many of the errors indicated below were corrected during the translation process.
Lines displayed in headings, signatures, combo boxes, list boxes, or tooltips/placeholders of the previous Russian interface follow a single rule: they start with a capital letter (as a positive example, it is enough to look at any well-known Russian application). In the new translation, everything is again brought to the common denominator of the original, where there is no single rule: somewhere lines start with capital letters, somewhere with lowercase letters:
Example of signatures starting with a capital letter in both the original and the translation:
change_card_background:
title: "User Card Background"
instructions: "Background images will be centered and have a default width of 590px."
Example of signatures starting with a lowercase letter in the original and in the latest translation (before/after):
- instructions: "Иконка, появляющаяся в правой нижней части изображения вашего профиля"
+ instructions: "значок рядом с аватаром"
- reviewable_items: "Сообщения, требующие рассмотрения"
+ reviewable_items: "элементы, требующие проверки"
- every_30_minutes: "Каждые 30 минут"
- every_hour: "Каждый час"
- daily: "Ежедневно"
- weekly: "Еженедельно"
- every_month: "Каждый месяц"
- every_six_months: "Каждые шесть месяцев"
+ every_30_minutes: "каждые 30 минут"
+ every_hour: "каждый час"
+ daily: "ежедневно"
+ weekly: "еженедельно"
+ every_month: "каждый месяц"
+ every_six_months: "каждые шесть месяцев"
- sent: "Создано / Последняя отправка"
+ sent: "Создано / последняя отправка"
In the previous translation, where some phrases mistakenly ended with a period, they were removed; and vice versa, where periods should have been, they were added. The new translation does not take this into account - everything is duplicated according to the example of the original.
One of the examples:
- add_warning: "Официальное предупреждение"
+ add_warning: "Официальное предупреждение."If you do polls where users can select multiple options, the results show two numbers: the number of votes and the number of voters (with the former being weakly larger than the latter).
That distinction is entirely absent in Russian: both votes and voters are translated as голосов, which results in a confusing picture.
0 voters
Or how it looks in production:
This one is fixed now (I think it was fixed recently).
I agree that this translation should be corrected, we’ll ask the agency to do it.
Thank you for catching this. Turned out this is the old problem, but we’ll ask the agency to improve this place.
It’s a bit inconvenient for the others, though. Everyone else who will read this will need to translate this post, and sometimes translators may return results that are hard to understand. But to summarize: all the general notes about terminology, consistency and context definitely makes a lot of sense, but the agency is aware of these things.
We do agree that “Запись” isn’t a good translation for “post”, and the previous translation “Сообщение” worked much better, so it’s going to be fixed.
There are still problems with plurals, and we will ask the agency to pay more attention to it. Also, surely “Пожаловаться” will work much better for “flag” 
Speaking of the fact that the translations now follow the punctuation of the original, I believe this is a right thing. Sometimes our original strings may contain mistakes (for example they can use a dot at the end when in fact it would be better without it), but that mistake should be fixed in the original string.
Hi,
I wrote the reasons for which I wrote in Russian, IMHO that part of the text will be understandable and interesting only to the Russian-speaking part of the community, but ok - I’ll try in English.
First of all, I would like to thank the agency for updating the translation, especially for the file server.ru.yml.
Based on your translation, another version of Russification has been created here, it takes into account all the work done, but has been left the already familiar terminology that was used in the Russian translation until October 2022.
| En | RU (original) | RU (agency) |
|---|---|---|
| Post | Сообщение | Запись |
| Message | Личное Сообщение | Сообщение |
| Categories | Раздел | Категория |
| Summary | Сводка | Спойлер |
| Review | Премодерация | Очередь проверки |
| Admin | Администратор | Администрирование |
| Faq | Правила | Ответы на вопросы |
| Likes | Симпатии | Лайки |
| About | О Форуме | Информация (fixed partially) |
Since Russian terms are not the most compact, part of the translated text in the agency version is cut off, for example with the terms admin (Администрирование), FAQ (Ответы на вопросы) and review (Очередь проверки).
However, the translation does not always fit in the text field, in some cases it is duplicated with tooltips
/admin/customize/watched_words/action/block
But for some elements tooltips are not displayed and phrases remain truncated:
/admin/customize/permalinks
/admin/site_settings/category/required
It would be nice to add tooltips to all similar elements or increase their width if possible.
включён / отключён -> Используется/Не используется
/admin/badges/101
“Активаторы событий” → “Триггеры событий”
Partial use of Cyrillic in links looks at least strange:
payload_url_placeholder: "https://пример.com/postreceive"
from_placeholder: "отправитель@пример.com"
to_placeholder: "получатель@пример.com"
cc_placeholder: "копия@пример.com"
For example, for filters on the page /admin/logs/staff_action_logs
Отозвать письмо-> Отзыв письма
Changed the translation for watched words for the same purpose so that all items are displayed in the same style
require_approval: "Требовать одобрения" -> "Одобрение"
/admin/customize/watched_words/action/block
Another example for permissions:
group: "Группа"
see: "Просмотр"
reply: "Ответить" -> "Ответ"
create: "Создать" -> "Создание"
other: "Эта запись понравилась %{count} человека" -> Это сообщение понравилось %{count} людям
other: просмотреть %{count} скрытого ответа -> просмотреть %{count} скрытый ответ
many: байтов -> байт
other: байта -> байт
“Выпадающий список заголовка” → “Выпадающий список заголовков”
/admin/site_settings/category/navigation
"Основной" -> "Основное"
/admin
It’s fixed, so thank you.
But… If you now add “Hide details” (or spoiler bbcode)
while it’s still called spoiler (which is totally reasonable given how widespread the word is in this specific meaning) in the menu
the code that is inserted by default:
[details="Сводка"]
Этот текст будет скрыт
[/details]
mentions “Сводка” instead of “Спойлер”
[details="Спойлер"]
Этот текст будет скрыт
[/details]
which is probably a consequence of batch-translating all mentions of a spoiler to сводка. Or also an indication that they don’t understand that js.user.summary.title and js.composer.details_title contain information…
I don’t know why, but it seems like professional Russian translators have a shtick for modifying the meaning of the original text. It’s pretty annoying. So, what’s up this time?
Check out the description for the badge anniversary:
This badge is granted when you’ve been a member for a year with at least one post in that year. Thank you for sticking around and contributing to our community. We couldn’t do it without you.
The translation:
Эта награда выдаётся, когда вы являетесь участником сообщества в течение года и опубликовали хотя бы одну запись в этом году. Спасибо за то, что вы остаётесь с нами и вносите свой вклад в сообщество. Возможно, мы не смогли бы сделать этого без вас.
The first two sentences are fine. The last one says: “Perhaps we couldn’t have done it without you.” Asking in a civil manner, who decided that the word “perhaps” is warranted? It changes the tone of the whole thing from “humble gratitude” (which is appropriate given that the real value of the community is in the userbase) and “being friendly” to a condescending “okay, maybe we need you”.
A neural network does 10x better job than these “professionals”. From DeepL:
Этот значок выдается, если вы являетесь участником сообщества в течение года и за этот год написали хотя бы одно сообщение. Спасибо, что остаетесь с нами и вносите свой вклад в развитие нашего сообщества. Без вас мы бы не справились.
When you hover over a message in chat, you see the timestamp (the screen is with the language set to English (US)):
Same message on hover in Russian:
This seems to be set by js.chat.dates.time_tiny, and at first, I thought this was a translation issue with a parameter missing (like %s or similar), but in English it’s also simply “h:mm” (in Russian it’s set to “ч:мм”), so maybe this is more of lack of mapping from ч:мм to time? Or maybe this shouldn’t be translated at all, given that, well, why would you translate a number?
P.S. By the way, were public chat channels on meta removed?
- Эта награда выдается, когда вы являетесь участником в течение года с хотя бы одним постом в этом году. Спасибо за то, что вы остаетесь и вносите свой вклад в наше сообщество. Мы не могли бы сделать это без вас.
+ Эта награда выдается, когда вы являетесь участником сообщества в течение года и опубликовали хотя бы одно сообщение в этом году. Спасибо за то, что вы остаётесь с нами и вносите свой вклад в сообщество. Возможно, мы не смогли бы сделать этого без вас.
@hiddenseal
For the sake of justice I note that this error appeared in commit 71da5e0 (September 1, 2020), more than 2 years before the agency made the first translation, so it may have been my mistake that I did not pay attention to this.
On the other hand, the agency could have paid no attention to this when they replaced “сообщение” with “запись” in this paragraph.
Anyway, thanks for noticing. Already fixed in RAPIRA language files.
The sad thing is that the more significant mistakes made by the agency remain uncorrected, and these guys do not comment on the result of their work.
So much for making assumptions on my part. Sorry for the strong language 