I thought I was religiously following the document. But thanks for making me
read it again, I know where all have I goofed up

Thanks Karen

RS
On Tue, Jun 24, 2008 at 11:33 PM, Karen Tracey <[EMAIL PROTECTED]> wrote:

> On Tue, Jun 24, 2008 at 1:39 PM, Ramdas S <[EMAIL PROTECTED]> wrote:
>
>> What is the best strategy to get django read non-ascii characters? Or at
>> least stop it from displaying the horrible error claiming DjangoUnicode
>> Decode error?
>>
>
> Don't put non-ASCII data into bytestrings.  Rather use Unicode objects
> throughout your code.  Follow the checklist here:
>
>
> http://code.djangoproject.com/wiki/UnicodeBranch#PortingApplicationsTheQuickChecklist
>
> Follow the recommendations here:
>
> http://www.onlamp.com/pub/a/python/excerpt/pythonckbk_chap1/index.html
>
>
>> I usually end up cleaning the content. I do not think that is a great
>> idea, if I am letting thousands of users access and write content onto sites
>
>
> Use Unicode consistently throughout your code (as Django does internally
> post unicode-branch merge) and you do not have to avoid non-ASCII data in
> your content.
>
> Karen
>
> >
>


-- 
Ramdas S
+91 9342 583 065
My Personal Blog: http://ramdas.diqtech.com

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to