Malcolm Tredinnick wrote: > On Mon, 2006-09-18 at 00:22 +0000, coulix wrote: > > puting DEFAULT_CHARSET to utf-8 didnt solve the Ao? != Aôut > > Not that only Aôut orm date generation is liek this all other > > accesnts in the template are fine. > > I haven't been following this thread in all its gory details, but seeing > this comment reminds me of something: there are a couple of places where > we do some simple string truncation such as > > return MONTHS[self.data.month][0:3] > > (this is what the "M" date filter returns; see django.utils.dateformat, > line 152). > > Now, if month string is really a UTF-8 string with multi-byte characters > in it, this simple truncation will lead to problems. Interestingly, ô is > \xc3 \xb4 in UTF-8 and if you look at the source of the page (I grabbed > it with "curl -i ..." so that my browser didn't interfere at all), you > can see that the character displayed as "?" is \xc3. > > I have a vague memory that there was a ticket about this that was > originally closed as wontfix, but a unicode-aware solution should be > appropriate here. Anyway, I don't have a fix up my sleeve at the moment, > but it sounds a lot like that is the problem. > > Regards, > Malcolm
Oh i see !, well done. I will display the whole month then. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
