#24739: Undocumented i18n behavior change in 1.8 (or a regression)
--------------------------------------+------------------------------------
Reporter: drakkan | Owner: nobody
Type: Bug | Status: new
Component: Internationalization | Version: 1.8
Severity: Release blocker | 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 drakkan):
New behaviour:
- if a string is not translated for a locale django use the translated
string (if any) from the default locale
Old behaviour:
- if a string is not translated for a locale django use the untranslated
string for the some locale
what is most correct is an opinion, I like the old behaviour since all
untraslated string should be the same,
your opinion could be that an untranslated string should show the value
for the default locale and not the untranslated one
however is easy enouth to use a tool like poedit to copy all the
translations from the original string, so if you like more the new
behaviour is just a matter to document it
--
Ticket URL: <https://code.djangoproject.com/ticket/24739#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/065.6071b7402deb733a904a063b17477a16%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
