Re: [Django] #13764: i18n in custom javascript

[Django]

#13764: i18n in custom javascript
-+
 Reporter:  Sebastian Noack  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  contrib.admin|  Version:  1.2
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by Claude Paroz):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 I don't see this going anywhere. Probably add your custom jsi18n view in a
 custom `base_site.html` admin template.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.215aa9296a59348ea7cec5a4209141ed%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #13764: i18n in custom javascript

[Django]

#13764: i18n in custom javascript
---+
  Reporter:  sebastian_noack   | Owner:  nobody
Status:  new   | Milestone:
 Component:  django.contrib.admin  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  1 |  
---+
Changes (by russellm):

  * needs_better_patch:  0 => 1
  * summary:  i18n in custum javascript [PATCH] => i18n in custom
  javascript
  * stage:  Unreviewed => Accepted

Comment:

 I'm going to accept this as a problem description, but not as a proposed
 fix. The problem clearly exists, but moving i18n into a per-model
 definition seems like the wrong approach to me. This would result in a
 proliferation of little jsi18n scripts, when what you really want is one
 good script that is composed of all the little extensions. There's no
 reason these extensions can't be defined on a per-model basis, but I don't
 see why they need to be served on a per-model basis.

-- 
Ticket URL: 
Django 
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.