[android-developers] Should Plurals and Quantity Strings be used?

2010-09-20 Thread Greg Giacovelli
This feature has been around since cupcake, however it has always been
broken.
Bugs like, http://code.google.com/p/android/issues/detail?id=8287,
have been posted.

The things I am finding wrong with this is that it's completely
undocumented, and only works for english and czech in undefined ways.

The code suggests that the current implementation doesn't meet the
standards of what is desired and hasn't been changed since it was
added. However going forward is it better to just not use this
functionality and use a custom one off localization scheme for each
application? Has everyone just been rolling their own plural
mechanism?


-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


Re: [android-developers] Should Plurals and Quantity Strings be used?

2010-09-20 Thread Kostya Vasilyev
I recently used this mechanism in my app. It's localized for Russian, where
plurals conjugate (or is it congregate?) depending on the quantity: 2
through 4 have one ending, 5 and greater have another. Quantities like 22,
32, 123..2 are the same as just 2, except for 12 through 20. Quantities
ending with a 1 are same as singular. Perhaps Czech is similarly complex.

I ended up changing the way the message is worded, using an abbreviation to
sidestep this issue.

--
Kostya Vasilyev -- http://kmansoft.wordpress.com

21.09.2010 2:24 пользователь Greg Giacovelli miyamo...@gmail.com
написал:

This feature has been around since cupcake, however it has always been
broken.
Bugs like, http://code.google.com/p/android/issues/detail?id=8287,
have been posted.

The things I am finding wrong with this is that it's completely
undocumented, and only works for english and czech in undefined ways.

The code suggests that the current implementation doesn't meet the
standards of what is desired and hasn't been changed since it was
added. However going forward is it better to just not use this
functionality and use a custom one off localization scheme for each
application? Has everyone just been rolling their own plural
mechanism?


--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en