tag:blogger.com,1999:blog-4638805504123061057.post6567265403489845323..comments2008-05-29T13:26:57.486+03:00Alexeyhttp://www.blogger.com/profile/01888820688161272210noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-4638805504123061057.post-74845850400099241002008-05-29T13:26:00.000+03:002008-05-29T13:26:00.000+03:00I had "???" when i converted (from latin1 to UTF8) of japanese and other languages that should be encoded to UTF16/32 becausethey didnt have "symbols" in UTF8 table.<BR/><BR/>In case of UTF16/32 you need to do everything from beginning and replace UTF8 to UTF16 (or UTF32) respectively.Alexeyhttp://www.blogger.com/profile/01888820688161272210noreply@blogger.comtag:blogger.com,1999:blog-4638805504123061057.post-20228974300887617452008-05-28T17:34:00.000+03:002008-05-28T17:34:00.000+03:00Never mind. I was expanding what you wrote with a SET NAMES command and that seems to be what created the truncation issue.<BR/><BR/>Have you come across the ???? question marks caused by inserting data using a UTF8 client connection to a latin1 table. I haven't found a way to fix data stored in this fashion, do you know if it can be fixed?TPolhttp://www.blogger.com/profile/05660049272022485471noreply@blogger.comtag:blogger.com,1999:blog-4638805504123061057.post-12469674319403428282008-05-28T11:42:00.000+03:002008-05-28T11:42:00.000+03:00What exactly you mean ?<BR/>Exception ?Alexeyhttp://www.blogger.com/profile/01888820688161272210noreply@blogger.comtag:blogger.com,1999:blog-4638805504123061057.post-28171077507107631662008-05-28T00:00:00.000+03:002008-05-28T00:00:00.000+03:00I attempted your approach and found that data in fields defined as Text were truncated. Do you have any suggestions?TPolhttp://www.blogger.com/profile/05660049272022485471noreply@blogger.com