#13617: USE_L10N results in faulty javascript code in GeoDjango with some
locales
--------------------------------+-------------------------------------------
Reporter: piquadrat | Owner: jbronn
Status: assigned | Milestone: 1.3
Component: GIS | Version: 1.2
Resolution: | Keywords: L10N gis gmaps
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
--------------------------------+-------------------------------------------
Comment (by piquadrat):
Although I didn't change the component to "Template system", I have some
sympathies with the anonymous change. IMHO, this is a bug (or an
oversight, or a missing feature) in the template system, and the GIS
component is affected by the bug. Incorporating a workaround in the GIS
JavaScript code may solve the particular issue I did report in the first
place. But it doesn't solve the deeper problem that L10N can't be used
(bar some ugly workarounds) in a project that outputs strictly structured
information through the templating system.
--
Ticket URL: <http://code.djangoproject.com/ticket/13617#comment:11>
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 [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.
