#5886: documentation of _() syntax in templates is incomplete
-----------------------------------------------------------------+----------
   Reporter:  Dmitri Fedortchenko <[EMAIL PROTECTED]>            |              
  Owner:  nobody       
     Status:  closed                                             |            
Component:  Documentation
    Version:  SVN                                                |           
Resolution:  invalid      
   Keywords:  i18n internationalization templates documentation  |              
  Stage:  Unreviewed   
  Has_patch:  0                                                  |           
Needs_docs:  0            
Needs_tests:  0                                                  |   
Needs_better_patch:  0            
-----------------------------------------------------------------+----------
Comment (by ubernostrum):

 If that syntax works it should not and should not be relied on (though
 deliberately breaking it won't necessarily be a high priority). Again, the
 template documentation makes it clear that the template system is
 '''not''' Python, and that arbitrary Python syntax (such as function calls
 wrapped in parentheses) should not work and should not be tried. I'm not
 sure how that can be made clearer aside from drawing up and including a
 list of every conceivable Python function and every type of syntax people
 might try. Meanwhile, the i18n docs provide, again, a perfectly clear
 description of how i18n in templates works.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/5886#comment:7>
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to