This is for anyone out there storing Japanese characters along with English characters. I've searched everywhere for anything that has to do with my particular situation....with no progress. I'm stuck.
SUMMARY: The client recently requested that Japanese be stored in an otherwise standard English (Latin) MySQL database. Whereas all rows in the table used to be Latin only, now some rows store Latin and some store Japanese. I do not mix English with Japanese in the same row. Upon writing Japanese data to the database (web form -> ASP -> MyODBC), and then viewing the record on a web page, I discover that random Japanese characters are being 'morphed' into other, seemingly random, Japanese characters, and very occasionally, 'morphed' into a Latin character (so far just the letter "t"). With the exception of these few, random characters, all the Japanese data looks fine *when displayed on a web page*. This is a standard install of MySQL version 3.23.38-nt (on Windows 2000 SP2) - support for Japanese characters is installed by default, I assume. I also store Chinese and Korean characters in the same table, and those character sets are diplayed without error. Question 1. If I were to pull the Japanese rows out and put them in a separate table - what do I do to the table to 'configure' it as storing sjis characters without setting the default character set to the entire database? Question 2. How do I view Japanese records in the command line *in Japanese* to eliminate the possiblity that the culprit is somewhere outside of MySQL, for example: Microsoft IIS or ASP or MyODBC? DETAILS: Environment: I have one computer running Windows 2000 Service Pack 2, MySQL 3.23.38-nt, and the MySQL Driver for ODBC. Someone else installed MySQL on the machine - I confidently assume they took the defaults and did nothing in particular with configuration at install. The machine is a dedicated webserver, serving up ASP pages which retreive data from the MySQL database via MyODBC. Background: I've been successfully storing Latin characters in two fields, "title" varchar(255) and "body" mediumtext. The recently added Japanese content is stored in the same table as the English content. The content is entered to the database using a web-based content publishing tool: ASP pages with forms that submit to the MySQL database. The database content is displayed to the web site using ASP which retrieves from the database. As long as the client browser has proper language pack installed, the Japanese characters 'seem' to display nicely. The web pages for Japanese content uses Shift-JIS. I do not speak or read Japanese. I do not need to search or order by Japanese character fields (only date_modified or id, for example). Process for publishing Japanese content: I receive a MS Word document with Japanese content. I copy and paste content into web form in publishing tool. Web form submits data to database, creating a new record. User browses to Japanese page on my web site and sees database-driven Japanese content. Problem: Random Japanese characters are being 'morphed' into other, seemingly random Japanese characters, and very occasionally, a Japanese character will be 'morphed' into a Latin character. Once the content is published, at first glance, everything looks ok (its all just Japanese to me). However, if I do a character-by-character comparison between the MS Word doc and the data driven web page, I will discover that, for example, 5th, 12th, 134th, and 291st characters displayed on the web page are *different* from what I pasted in the the publishing tool. Most of these broken characters have been morphed to other Japanese characters, and a few morph into Latin characters (so far only the letter "t"). A Japanese speaking colleague confirmed that the web page read exactly as the Word doc, with the exception of these random 'morphed' characters. Thank you so much for taking the time to read this. I appreciate any input whatsoever. Sincerely, Dawn Friedland [EMAIL PROTECTED] --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
