Ivan Sagalaev wrote: > First of all, Gabor, thank you very much for doing this! >
thanks :) > gabor wrote: >> today i experimented a little with the django source code, >> and here are the results. >> >> if you apply a very small patch (65lines, attached), you can write a view >> completely in unicode. >> means: >> - GET/POST contains unicode data >> - request.META contains unicode data >> - you can put unicode text into the HttpResponse (this was already possible >> without the patch) > > Here's a problem that I didn't know how to solve last time this topic > was discussed. > > You can put unicode in HttpResponse. Does it imply that template > processing should be done in unicode too? I mean, should context data > be in unicode? yes > This would be convenient later because we will get all > the data from DB in unicode also. But this poses a problem of encoding > of actual template files. > > We need to know the encoding of a template file. This can be done by > just mandating that they should be in settings.DEFAULT_CHARSET or we > should create a new setting (TEMPLATE_CHARSET). The reason of having > two different settings is that enforcing default UTF-8 in templates > means enforcing people to use unicode-aware text editors that are not > that common. hmmm.. are you sure that the situation with unicode-aware editors is so bad? could you name some non-unicode-aware editors? for me it seems that from notepad through vim to eclipse everything does unicode fine... gabor --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
