On 18/04/07, mamcxyz <[EMAIL PROTECTED]> wrote: > > > Yes, instead of naming your models with "funky" characters, you can > > always set the verbose displayed name to whatever you need it to be. > > The are not funky. Are the normal characters in each labguage. Anyway, > that show too if the "funky" chars appear in "text" so....
Ah, so I've misunderstood what the problem is. I usually try to make everything in utf-8 from the very beginning, since I've had a lot of encoding issues in past projects, so when I encounter these errors the usual suspect is mixing Unicode and non-Unicode strings. As long as you keep that consistent and set your encoding correct, things will be pretty much OK. But I have to agree with Malcolm here - adding a default would just result in people asking the reverse question - "why does my code break in configuration X?". --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
