#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 claudep):
Replying to [comment:7 cristianocca]:
> Example (high level, no actual code)
>
> - using message ids that are actually codes rather than text, but can be
done with any case where the actual msgstr is not always the same as msgid
for your default language (another example, if you do not use unicode
characters as msgids for some reason like not wanting unicode on python
code strings, so you always need the msgstr value even for default
language for translations that have unicode characters)
(...)
I'm not convinced by either use case, having codes as msgid is IMHO very
bad practice, and avoiding Unicode is a thing from the past. I really need
a legitimate use case to accept this.
--
Ticket URL: <https://code.djangoproject.com/ticket/26337#comment:8>
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.d54d6dd60ab58f2da3c536395213f839%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
