#9118: Unhelpful handling of UTF_8 encoding bugs in ModelForm field.help_text
-------------------------------+--------------------------------------------
          Reporter:  jbl1      |         Owner:     
            Status:  closed    |     Milestone:  1.1
         Component:  Forms     |       Version:  SVN
        Resolution:  wontfix   |      Keywords:     
             Stage:  Accepted  |     Has_patch:  0  
        Needs_docs:  0         |   Needs_tests:  0  
Needs_better_patch:  0         |  
-------------------------------+--------------------------------------------
Changes (by jacob):

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

Comment:

 I'm not quite sure what Django can do better here; if you've got an
 invalid encoding in your source file, that's on you.

 The reason you're not getting an error in the template is because it's
 generally the policy that invalid data shouldn't cause the template
 rendering to break. That's mostly a good policy, and we can't change it
 even though in this particular case it's causing more harm than good.

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

Reply via email to