Elim Qiu <elim....@gmail.com> wrote: >> I just start try django 1.3.1, still in the step I of the tutorial, >> but noticed that the tables created is in latin1 encoding while I >> prefer utf8 for the entire app. > > This https://docs.djangoproject.com/en/dev/ref/unicode/ > > would suggest that making the table UTF8 should suffice.... > Thanks a lot Lachlan Musicman, I'll go a head to try this.
>> I don't want to set the database default char encoding to be utf8 >> since I have other non-django apps. > > That will break if the DB is UTF8? > Yes. For example, Simplified Chinese typically use an ecoding GB2312, apps using it will display utf8 Chinese as unreadable things... Since my other apps will not share data with django, make django utf8 friendly should be enough. -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
