I welcome the pedantics! > Multiple databases on multiple servers? That is what I thought...which I assume means multiple machines (not an option). And I'm glad you pointed it out that it still wouldn't solve the problem.
> Go re-read the section of the manual on string literals. Ask > yourself what is going to happen when you try to insert the text > > Our network switches are 100% "standard"! > > or > > You should store your preferences at c:\WINNT\bloopers\prefs.txt > > in your database. How would you set up the database queries > to store those strings? Prior to sending the string to the database, I would look for "\" and replace it with "\\". Its difficult for me to see the "\" in "Our network switches are 100% "standard"!" because, like you said, the 0x5c may be only part of the entire hex value of the character (as Japanese characters are multibyte). I would need to first convert the Japanese character to hex, then look for the "0x5c", then replace it with "0x5c0x5c". Problem solved. > Say, do you want a little utility program in Java or C that > will print the hexadecimal values of the characters in a > string? I avoiding the 0x5c byte *precisely* because I don't know how to convert my Japanese text (squiggly pictures I see in Notepad) into their hex values. I would LOVE such a utility! This issue is so baffling to me because 1. People on this list have said they have successfully stored multiple charsets, including Japanese, in the same database. 2. I store Korean and Chinese (simplified) in this same database with no errors. (Of course, I am dependent on the Korean and Chinese speaking colleagues of my client whom were tasked with proofreading.) 3. A fellow from MySQL with whom I was recently in contact with off-list said the following: "Right now, MySQL does not enable you to store multiple charsets per database." (This same fellow said the 0x5c was probably causing my problem.) Thanks for all your help. I feel much less hopeless than I did several weeks ago. Dawn Friedland [EMAIL PROTECTED] > -----Original Message----- > From: Joel Rees [mailto:[EMAIL PROTECTED]] > Sent: Sunday, September 29, 2002 7:24 PM > To: Dawn Friedland > Cc: [EMAIL PROTECTED] > Subject: Re: Japanese Charset > > > Dawn, I'm going to give in to the temptation to be pedantic. > Apologies in advance. > > > Kirk Samuelson wrote: > > > I've read lots of similar posts in the archives at > > > <http://lists.mysql.com/>. Many suggestions to use a BLOB > > > instead of a > > > text field. But MySQL supports double-byte languages. Why > not use an > > > encoding it supports (SJIS or UJIS for Japanese) instead of this > > > kludge? If I compile MySQL to support UJIS with > --with-charset=sjis > > > won't text fields then store ujis encoded text properly? > I'd like to > > > use Unicode too but if it's not supported yet... > > > > The idea is to be able to store Latin and Japanese in the same > > database (as well as Chinese & Korean). Isn't that > supported by MySQL? > > People on this list say they've done it successfully. > > > > If I compile MySQL using --with-charset=sjis , how will it > handle the > > Latin, Chinese, and Korean characters? > > Multiple databases on multiple servers? > > But you still have the problem of needing to handle the > escape characters correctly. > > (Sorry I wasn't able to get that page up over the weekend.) > > Go re-read the section of the manual on string literals. Ask > yourself what is going to happen when you try to insert the text > > Our network switches are 100% "standard"! > > or > > You should store your preferences at c:\WINNT\bloopers\prefs.txt > > in your database. How would you set up the database queries > to store those strings? > > Say, do you want a little utility program in Java or C that > will print the hexadecimal values of the characters in a > string? Basically, it would be a command-line utility, so you > would copy the text and then paste it into the command line, > after the name of the utility. You'd need a compiler, of course. > > -- > Joel Rees <[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
