#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
--------------------------------------+------------------------------------
Changes (by Carlton Gibson):
* needs_better_patch: 0 => 1
* needs_docs: 0 => 1
Comment:
I've given this an initial look but without a clearer consensus that it's
the right approach I'm not sure what to say.
I'll look again but I would like to see positive agreement on the
discussion thread (which is already too long...)
before committing to the approach.
That's the main issue.
Then, just on the PR, the docs changes don't explain what's going on
clearly. The new settings and makemessages options don't have a ''Why''
you'd use them anywhere.
(That discussion is here and in the mailing list, but it needs to be clear
for someone installing the new version.)
Once those are in place, release notes.
Finally the PR needs a bit of a tidy, and they'll no doubt be nitpicks but
I want to sort out the more fundamental issues before we spend energy
there.
--
Ticket URL: <https://code.djangoproject.com/ticket/30439#comment:37>
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.7f4e7f10885caaa567fa18b7cdb6ba93%40djangoproject.com.
