On Mar 21, 4:19 pm, "Karen Tracey" <[EMAIL PROTECTED]> wrote: > OK, got it now. Turns out the answer is in the clear-as-mud error message, > sort of: > > Warning: Incorrect string value: '\xF0\x90\x8C\xBC\xF0\x90...' > > x'f0908cbc' is a valid 4-byte UTF-8 value, only MySQL doesn't support 4-byte > UTF-8. Its 'utf8' character set only supports up to 3-byte UTF-8, see: > > http://dev.mysql.com/doc/refman/5.0/en/charset-unicode.html > > Support for 4-byte UTF-8 is listed near the top of what's coming in 6.0: > > http://dev.mysql.com/doc/refman/6.0/en/mysql-nutshell.html > > I've seen references to turning off strict mode in MySQL to get rid of > problems like this, but haven't played with that at all. I'm not sure what > MySQL will do with the problem data if you turn off strict mode. > > If you want to just remove the problematic 4-byte UTF-8 codes from the file, > they're only present in the Gothic (line 47) and 2nd Vietnamese (line 123) > of the "I Can Eat Glass" translations. Without those two translations MySQL > accepts the data. > > Karen
For those of us having a very similar problem elsewhere, what's a good general solution? 1. Check that the table is indeed utf8. 2. ??? Does attempting to re-encode the UTF8 string work? Try the mysql strict mode thing you mentioned? Thanks, Rob --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
