11

Android allows translators to define Plurals. The following example works for me with locale 'en':

<plurals name="numberOfSongsAvailable">
    <item quantity="one">One song found.</item>
    <item quantity="other">%d songs found.</item>
</plurals>

But adding a special value for two does not work, still the other version is taken. Is the usage of two dependent upon the locale? So does Android only take the two version if the locale explicitly specifies that there should be a two version?

The SO Question Android plurals treatment of “zero” spots the same mistake when using zero in English which is also not supported. There are no solutions in this question except to avoid Android plurals which I want to avoid.

Community
  • 1
  • 1
theomega
  • 31,591
  • 21
  • 89
  • 127
  • Yes, the usage of two is specific to locale. Just because you give it the number 2 does not mean that it will use quantity="two". It will only use that quantity for languages that have special cases for the number 2 – ByteMe Apr 04 '12 at 01:51
  • possible duplicate of [Android plurals treatment of "zero"](http://stackoverflow.com/questions/5651902/android-plurals-treatment-of-zero) – Paul Lammertsma Mar 12 '13 at 23:07

3 Answers3

10

Android is using the CLDR plurals system, and this is just not how it works (so don't expect this to change).

The system is described here:

http://cldr.unicode.org/index/cldr-spec/plural-rules

In short, it's important to understand that "one" does not mean the number 1. Instead these keywords are categories, and the specific numbers n that belong to each category are defined by rules in the CLDR database:

http://unicode.org/repos/cldr-tmp/trunk/diff/supplemental/language_plural_rules.html

While there appears to be no language which uses "zero" for anything other than 0, there are languages which assign 0 to "one". There are certainly plenty of cases where "two" contains other numbers than just 2.

If Android where to allow you to do what you intended, your applications could not be properly translated into any number of languages with more complex plural rules.

miracle2k
  • 29,597
  • 21
  • 65
  • 64
3

Yes, the usage of two is specific to locale. Just because you give it the number 2 does not mean that it will use quantity="two". It will only use that quantity for languages that have special cases for the number 2

From http://developer.android.com/guide/topics/resources/string-resource.html#Plurals:

Note that the selection is made based on grammatical necessity. A string for zero in English will be ignored even if the quantity is 0, because 0 isn't grammatically different from 2, or any other number except 1 ("zero books", "one book", "two books", and so on). Don't be misled either by the fact that, say, two sounds like it could only apply to the quantity 2: a language may require that 2, 12, 102 (and so on) are all treated like one another but differently to other quantities. Rely on your translator to know what distinctions their language actually insists upon.

ByteMe
  • 1,436
  • 12
  • 15
3

That's an old bug. There are just a few missing if-clauses in the relevant code section of the PluralRules class.

As the answer in your linked question stated, you are better off by using MessageFormat or something else. The bug has been reported in may 2010, I wouldn't expect that beeing fixed in the near future (and you still have a faulty version on old version devices in this case).

Completely false, see the comments.

Community
  • 1
  • 1
  • 2
    I read this Bug and it is simply wrong: The Bug does not exist anymore as the `PluralRules` class does not exist anymore on recent androids. Instead a libary `libcore.icu` is used. The code linked in the bugreport is very old. See the recent code here: https://github.com/android/platform_frameworks_base/blob/master/core/java/android/content/res/Resources.java – theomega Dec 12 '11 at 16:09
  • 2
    Although you are correct: It doesn't help that they use a new Code for this, it has the same errors (see question) and old versions still have the old code. So thanks for your answer! – theomega Dec 12 '11 at 16:18
  • So. How do I deal with this on older android versions? Is there something in android support package? Or do I need to just work around it and stop caring? – Arie May 25 '12 at 11:35