Plural issues on Android due to update to CLDR 41 about translate HOT 8 CLOSED

Presently, this list is shared for more file formats, so probably a separate one is needed for Android to stick with CLDR 38. The previous version was CLDR 37, so some additions in the PR are needed for Android as well.

As for Weblate, it will need additional definitions in https://github.com/WeblateOrg/language-data/ to match this (it currently uses the latest CLDR as well).

from translate.

...which is now Won't Fix (Obsolete), what really doesn't explain anything.

Anyway, Android seems to be upgrading CLDR frequently, the question is how to deal with that:

• Keep separate rules for Android and update them when Android with updated support is released. This is more accurate, but also requires more maintenance.
• Always follow the latest CLDR and ignore the differences. Android will follow up at some point anyway.
• Update CLDR data once it has been released in Android. This will postpone it for everybody else.

This was merely a non-issue before changes in CLDR 38 – the only changes were additions of new languages, so it didn't break existing ones. In recent CLDR releases, rules for existing languages are changing and that makes it harder to deal with.

from translate.

@emmapeel2 That is definitely not related to plural definitions, please open a separate issue here: https://github.com/WeblateOrg/weblate/issues/new?assignees=&labels=&projects=&template=bug_report.yml

from translate.

Hm, it seems that Android 13 has been updated with CLDR 40 plurals: https://developer.android.com/about/versions/13/features#unicode
(that just hasn't been added to the table I found above yet).
So then it might be a bug in Android Lint that it still complains about the many plural type...

from translate.

reported on Google's issue tracker: https://issuetracker.google.com/issues/280634462

from translate.

For the OnionShare Android component we are having issues with the plurals. We have the add-on Remove blank strings , but the plurals for some untranslated languages are added, even when empty, by weblate:

onionshare/onionshare-android@627ce62#diff-96cbab6d6c22855d341211d7bcbbed33456020f2d8ad707a1fb3905cc35e5dff

from translate.

@emmapeel2 That is definitely not related to plural definitions, please open a separate issue here: https://github.com/WeblateOrg/weblate/issues/new?assignees=&labels=&projects=&template=bug_report.yml

Ok, this is the new ticket: WeblateOrg/weblate#10887

from translate.

I don't think there is a good way to address this. As there is no reliable way to recognize which plural rules the strings file is using, we can only make assumptions. And assuming it is using a current standard is IMHO better than assuming it uses something older. Android is usually quite fast in adopting CLDR changes, and so we are, so I think the best is to keep things as they are right now. There might be some period in time when the tools will disagree.

from translate.