On Fri, Aug 31, Anderson Santos wrote: > > Ahhh, finally!
Fine! > > Thank you very much, it worked now =D > I didn't know about the __unicode__ trick Well, the unicode documentation is dense to read, so one shouldn't rush through it. But it contains also this trick: http://www.djangoproject.com/documentation/unicode ;-) > > And I am not sure if it is it that you want to know, but I still not > using the encoding header on the top of the files. I thought it was > more to the enconding chars of the file and not an advanced settings > for the application. Should I put it on the top of all my files? You're right, it only specifies the encoding of the source file, but: - Django assumes utf-8 in bytestrings, so you should better use an utf-8 encoding in your sources - Python needs to know the encoding of the source file when you use unicode literals such as u'ä'. Without source encoding declaration, python assumes latin-1. Gotcha ;-) Michael -- noris network AG - Deutschherrnstraße 15-19 - D-90429 Nürnberg - Tel +49-911-9352-0 - Fax +49-911-9352-100 http://www.noris.de - The IT-Outsourcing Company Vorstand: Ingo Kraupa (Vorsitzender), Joachim Astel, Hansjochen Klenk - Vorsitzender des Aufsichtsrats: Stefan Schnabel - AG Nürnberg HRB 17689 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
