#26337: Translations - No fallback used if requesting english variant
-------------------------------------+-------------------------------------
Reporter: cristianocca | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Documentation | Version: 1.9
Severity: Normal | Resolution:
Keywords: i18n translations | Triage Stage: Accepted
english |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by cristianocca):
Hi, I’m not really good at writing but here’s an attempt.
I would put some note somewhere starting from here, probably after msgid
and msgstr definitions:
https://docs.djangoproject.com/en/dev/topics/i18n/translation/#message-
files
“Due to certain limitations of the GNU gettext toolset, English have a
special treatment. Make sure all your English (and variants) translation
files correctly define a msgstr value and do not rely on your default
language as fallback, or you may experience unexpected results such as
msgid being returned rather than the default language msgstr (which might
or not be the expected result).”
Would that work, makes any sense at all?
--
Ticket URL: <https://code.djangoproject.com/ticket/26337#comment:5>
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/070.762da5b80f14a7d8a8bd8bc429f4354f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
