Dear Russian speaking community!
Currently, Russian translation cannot be finalized because there are some issues that need your attention and approval. If you run a Russian version of Discourse, you should have noticed that the home page has many untranslated strings here and there that spoil the page:
While I’ve discussed my proposed solutions with some Russian-speaking developers this side, a confirmation from Discourse community is still needed, so please either support or criticize but do not pass by if you speak Russian.
For translations to be possible, there is a function which returns a
translation key based on a number.
For example, for English there are only two keys:
2, 3, 4, … =>
Thus, there are only two versions of any string in English - for one and for many things.
% cats =>
For every language, a particular set of keys can be defined in order to allow translators to pluralize strings correctly. So, some languages need only 2 keys, but others, as Russian, need 3 or even more.
So, we have to translate, for example,
% message(s) to Russian:
- 1 сообщение (the suffix is e)
- 2 сообщения (the suffix is я)
- 3 сообщения
- 4 сообщения
- 5 сообщений (the suffix is ий)
- … and so on
We can see that there are 3 versions, and they cover all possible numbers.
There are currently 2 problems with pluralization keys for Russian:
Problem 1. There are 4 keys while we need only 3. The keys are:
one, few, many, other
Problem 2. The current keys are not intuitive and make no sense.
While it may seem that
few is for 2 to 4 (
2,3,4 сообщения), it is actually wrong because 15102 will also use the same suffix -
15102 сообщения, but it is nowhere near
So, while there are 4 keys in the system instead of 3, and while the keys are named not intuitively, we will continue struggling bad and/or incomplete Russian translation for Discourse.
I want to fix it once and for all and to finalize the Russian translations, but I cannot before you, the community members, say YES for the solution described below, or critisize it - that’s what Discrouse team requires!
The solution is simple - I propose to use 3 keys: one, two and five.
Firstly, it covers all possible keys, which can be seen here: Edit fiddle - JSFiddle
Secondly, I guess it should be very intuitive for any translator to understand which translation to make for which key.
While it is not clear what is difference between
many (old keys),
it is very clear what is
five (proposed keys).
So for example for
% message(s) we will have 3 keys with the following Russian translations:
While for English we have only two keys:
Now what is important is your opinion.
If you would bee a translator, would you understand what translation to write in a box like this?
Please vote, and if you don’t like the idea, then please propose your own keys!
- I support
one, two, five
- I support
one, two, other
- I want to keep
one, few, many
- I want to propose a better idea (please explain in a reply to this topic)
- I do not understand what this all is about
- I would like to vote, but the explanations above are unclear and confusing!
Thank you for your time and attention.