ops. my wrong. so the only way to keep it "clean" is using i18n. might be an overkill for small apps in one languange though.
On Apr 19, 1:46 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Thu, 2007-04-19 at 10:45 +0000, ashwoods wrote: > > 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. > > This isn't true. It's even verifiable with a one-line program. Having, > either > > a = '' > > or > > a = u'' > > in your source file will trigger a warning from python if you don't have > an encoding declaration. > > Regards, > Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
