ah, i code for english, german, spanish. :) but as far as i know, the encoding declaration is only needed if you have special chars in _code_ as opposed to strings. your strings can be unicode without having to declare an encoding for the python file.
my opinion is that if you can, you should even choose model names, function names, etc.. not only without special chars, but also in english, even more so in the opensource world. the part that the user "sees" can be translated using verbose name, or I18N. using english and no funky chars ensures that your code works well for others too. i always use snippets of code from here or there. just imagine how much work and time i would need just to understand the code if everybody writes code in their language, or if i use other code as libraries with classes in different encodings... cheers, ashley On Apr 18, 5:03 pm, Atilla <[EMAIL PROTECTED]> wrote: > 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 -~----------~----~----~----~------~----~------~--~---
