#13859: respect LANGUAGE_CODE in management command instead of overriding it
with
'en-us'
---------------------------------------------+------------------------------
Reporter: tonnzor | Owner:
Status: new | Milestone: 1.3
Component: django-admin.py | Version: SVN
Resolution: | Keywords:
Stage: Design decision needed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------+------------------------------
Comment (by fheinz):
Replying to [comment:7 tonnzor]:
> As you see - codename is in English and may be - and it is done - easily
parsed - that should stay English for sure.
> "name" is human-readable name that is not used for parsing and SHOULD be
translated into the user language.
While I agree that this info should be shown to the user in translated
form, I don't think it's reasonable to do so by storing a localized string
in the database, but rather by translating it in the UI. Storing the
human-readable name in English makes sense, because it makes it easy to
provide translations for all languages, while if you store this kind of
info in the local language, you can no longer provide a translated string
to a user with a different locale.
If the issue that prompted you to report this as a bug is similar to this,
maybe you should reconsider the wisdom of storing structured data in
localized form.
--
Ticket URL: <http://code.djangoproject.com/ticket/13859#comment:9>
Django <http://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 post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
