Add human readable formulas for Plural forms on +translate pages

[Carlos Perelló Marín]

Right now, Rosetta shows plural forms formulas as the system uses them. For people used to work with them is not a big problem to understand such formulas, but Rosetta targets people that don't need to know such low level details and we confuse them.

We should implement a way to 'translate' those plural forms into something more readable or at least document it quite well so there is not doubt about what to do with that information

[Noirin Shirley (noirin)]

It might be useful to only show this information where there's actually a number variable involved? Having it in the left nav, when I couldn't see any numbers or variables anywhere, confused me a lot, even though I pretty much understand the maths/formula!

[Sergey Kirienko (skirienko)]

You could see the way how poEdit (http://www.poedit.net/) do such thing.
It just shows an example of a number for every form: "form[0] (for example: 1), form[1] (for example: 2)), form[2] (for example: 5)". It is VERY useful.

[Adi Roiban (adiroiban)]

I think that the poedit implementation is good enought.

Maybe a better example is to have this string

form[0] - "eg. 1 thing"
form[1] - "eg, 2 things"
form[2] - "eg. 100 things"

[Łukasz Jernaś (deejay1)]

Maybe a better idea would be having it so like Linguist does; instead of [number] just say Singular/Plural/Paucal for known languages. It shouldn't be up to the translators to look up the gettext manual and even there it's hard to find...

[Ursula Junque (ursinha)]

Bug 208116, bug 90322 and bug 156107 will all be fixed at once.

[Данило Шеган (danilo)]

Actually, this bug is about plural forms on translate pages: it's something Henning will be using Ursula's code to render them, but it's a separate task and will go well with his +translate rework.

[Данило Шеган (danilo)]

Łukasz, examples work much better. For instance, Serbian has 3 plural forms, and I am certain majority of people don't know their grammatical names.

[Данило Шеган (danilo)]

We do have the code now on languages page which displays this more nicely. We should make use of it for the +translate page as well.

[Adi Roiban (adiroiban)]

Here is a mockup.
If everyhing is OK I can try to implement it.

[Данило Шеган (danilo)]

The current UI is already over-crowded. Adding more information, no matter how useful otherwise, would just reduce usability of the page imo. Henning has started work on re-implementing the entire set of +translate pages.

[Robert Collins (lifeless)]

This is a nice-to-have, but not in the current roadmap.