It shouldn't, if all you're doing is saving and redisplaying Unicode characters between the database and your site, you should be fine in that regard. I believe a lot of the issues come up when you're trying to use string comparing and modifying functions that aren't Unicode safe.
PHP isn't Unicode ready and I've been saving and displaying Unicode Japanese, Chinese and Korean for a good while now (since I started using mysql 4.1.x). But I don't do any comparison operations, or use anything that depends on the length of the Unicode string. I'm currently displaying Unicode strings in my Django site, but haven't messed with editing the strings yet. I'm no Unicode expert though, and I trust that the Django devs (and contributors) are much more familiar with the issues at hand than I am. Just wanted to chime in with my own experiences. :) Jay Sean Schertell wrote: > I'm planning to do two large bilingual sites (english/japanese). Does > django's lack of unicode support mean that I won't be able to collect > form data from utf-8 pages? > > Sean > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
