#29144: `DjangoTranslation.merge` loses catalog fallbacks
-------------------------------------+-------------------------------------
Reporter: Patryk Zawadzki | Owner: Patryk
| Zawadzki
Type: Bug | Status: assigned
Component: | Version: 2.0
Internationalization |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Patryk Zawadzki):
Matt, I gave it some thoughts before settling with the simplest solution.
I think the current behavior is the expected one in most real-life cases.
You have a base German translation in one app and override parts of it in
a project-wide translation. If the app provides Austrian German overrides
for strings that your project-level German translation overrides then they
are likely no longer relevant and would end up misleading so I believe
it's fine to expect you to have to override them again in a project-level
Austrian German translation. Going the other way you have to deal with all
sorts of fallback corner cases like what to do when the app provides full
`de-de` and `de-at` but no `de` while the project provides an incomplete
`de` translation with sparse `de-at` overrides.
--
Ticket URL: <https://code.djangoproject.com/ticket/29144#comment:3>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.c0d794ec000f49de99783dfdafc7c128%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
