#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: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Michal Čihař):
Replying to [comment:39 Claude Paroz]:
> At last, I took the time to try
[https://github.com/django/django/pull/12332 implementing support] for
different plural strings for the same language.
>
> I would appreciate testing from affected languages.
Looks good, I will try to find time for testing this.
Replying to [comment:40 Rodrigo]:
> Your implementation looks good, the problem with "dict-merge" (what you
implemented) is that updates in Django won't reach users unless something
triggers it externally. Users' catalogs would live under a different key
than the updated Django main catalogs, ignoring the updated plural forms.
I'd say this is expected behavior for me. I don't want Django to anything
more than `msgmerge`. Changing plural forms might need adjustment in the
translations as well and can't be done safely automatically.
--
Ticket URL: <https://code.djangoproject.com/ticket/30439#comment:41>
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.0350dac9f87d9e4d1d4616820275998d%40djangoproject.com.
