I have to search again to filter only the non ascii chars in the comments. Right now I have a list of all non ascii characters. But I am considering upgrading to 1.4 before that not only for the translations. If not, or if the problem still exists by then I will search for the exact template. Thanks for your help, much appreciated.
On Tuesday, March 26, 2013 4:07:02 PM UTC+1, Ramiro Morales wrote: > > On Tue, Mar 26, 2013 at 9:23 AM, Bastian <bastien....@gmail.com<javascript:>> > wrote: > > If I understand well, your fix is used to allow non ascii characters in > the > > comments of a template. I found non ascii characters outside comments > too, > > won't this break also? > > Unfortunately we don't have information about which template file is the > one > triggering the issue. > > it would be great if you could isolate it and create a simple test case. > > Non ASCII characters in non-comment template content should be handled > transparently. > > -- > Ramiro Morales > @ramiromorales > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
