#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 Rodrigo):

 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.

 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.

 Plural forms are only generated/copied once the catalog is initialized
 with makemessages, otherwise the messages will be updated only, see
 
https://github.com/django/django/blob/master/django/core/management/commands/makemessages.py#L616

 You shouldn't trigger a plural forms copy on each write_po_file because it
 may mess with the forms unexpectedly, i.e. if a plural form changes its
 "meaning" (ordering). Under a plural forms change, the catalog should be
 reorganized.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/30439#comment:40>
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.46fc86664700c8ad98ab3d3bb20f333b%40djangoproject.com.

Reply via email to