#4030: internationalization - auto translation of LANGUAGES
-------------------------------------+--------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: akaihola
Status: new | Component:
Internationalization
Version: SVN | Resolution:
Keywords: LANGUAGES settings.py | Stage: Ready for checkin
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-------------------------------------+--------------------------------------
Comment (by akaihola):
In my patch, I add a new template tag for this in order to not break
backwards compatibility.
I have these questions in my mind about this:
* is a separate template tag a good idea?
* should we worry about performance if we assume this tag could be used
on every page of a site in the base template -- is activating each
language in a loop a heavy operation?
* should the resulting list be cached?
* could the translations be fetched without activating each language in
its turn?
* is the list of dicts return value a sensible choice, or should we
return a list of tuples like in {% get_available_languages %} and only
include the language name in the language itself?
--
Ticket URL: <http://code.djangoproject.com/ticket/4030#comment:6>
Django Code <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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
