#30439: Translations issues on Django upgrade due to unexpected changes in
plural
forms
--------------------------------------+------------------------------------
Reporter: Michal Čihař | Owner: Rodrigo
Type: Bug | Status: assigned
Component: Internationalization | Version: 2.2
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Rodrigo):
Replying to [comment:21 Claude Paroz]:
> Replying to [comment:20 Rodrigo]:
> > > The main coding direction of this ticket currently is to not merge
translation catalogs at runtime if plural form count is different.
> >
> > Raise an error or log a warning and ignore the catalog?
>
> The idea is to keep several translation catalogs per language (one per
plural form?), and successively try to get a translation from each
catalog. This is described in comments above, please re-read them.
Alright, but this is not inline with django supporting only one plural
form as stated in docs.
If so, the ticket should be "Multiple plural forms support for i18n" ("Add
support for variable number of plural forms in Django in order to support
different translations platforms outputs")
--
Ticket URL: <https://code.djangoproject.com/ticket/30439#comment:23>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.84dfc98a8e6c15623e17c107982dd063%40djangoproject.com.
