Hello! gabor wrote: ... > this way works perfectly: > - have EVERYTHING in utf8 ...
Sadly not so :( There are some places in Django that prohibit you from using utf8 (any multibyte encoding in fact) - already mentioned admin's `last change` list is one of those places. For example, see contrib\admin\models.py, line 12: ..., object_repr[:200], ... Unicode or plain ASCII str `object_repr` there would be fine. But utf8-encoded `object_repr` easily becomes garbled. Couldn't be said better: > everytime when you are really > "processing" the data (shortening it to a given length, iterating over > it character-by-character, etc..) then first you have to convert your > text to unicode-strings, do the processing, and then convert back to > byte-strings Good luck! libraM --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
