#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 אורי):
Replying to [comment:3 Michal Čihař]:
> The very same situation happens with third party app localization (this
is where I noticed it first). I think it's not reasonable to expect
everything will use same plural forms.
Hi,
I understand the problem better now. Michal is correct, changes in one .po
file should not affect other .po files. I don't need more than 2 forms
(one singular, one plural) in my translation file and it makes things
complicated. Running makemessages in Django 2.2 doesn't change my po
files. I can't edit each file manually and add a third and fourth strings,
which are identical to the second. I prefer to keep using Django 2.1 until
this issue is resolved. I can understand now that in some languages more
than 2 forms are required, which may be also the case in Hebrew, but at
least I want to keep what worked until now to keep working. If I decide to
introduce more plural forms later, let me do it manually in my own .po
files and don't force me to rely on changes to the .po files of Django. I
don't think it makes sense that one .po file (the first one loaded) is
more "important" than others and would force all the other .po files to
change because of changes in the first file.
--
Ticket URL: <https://code.djangoproject.com/ticket/30439#comment:27>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.aeb13d7afd9057d2ff188799df730d28%40djangoproject.com.
