> -----Original Message----- > From: edwardspl@xxxxxxxxxx [mailto:edwardspl@xxxxxxxxxx] > Sent: Saturday, September 06, 2008 9:41 AM > To: mysql@xxxxxxxxxxxxxxx > Cc: php > Subject: Problem of Connection Character Sets and Collations > > Dear All, > > For displaying with unicode Character Sets problem : > > MySQL : > Command line of mysqldump and mysql : > Which command line is right ? > 1, --default-character-set=utf8 > 2, --default-character-set=utf-8 MySQL question. There's got to be a mailing list on http://www.mysql.com . > phpmyadmin : > The Connection Character Sets and Collations setting : > Which command line is right ? > 1, utf8_bin > 2, utf8_general_ci > 3, utf8_unicode_ci PHPMyAdmin question. PHPMyAdmin, while written in PHP, is not PHP. This would be like asking Internet Explorer questions in a Visual C/C++ mailing list/forum. > php : > Which command line is right ? > 1, mysql_query("SET NAMES utf8"); > 2, mysql_query("SET NAMES utf-8"); Again, a MySQL question. I have to admit, though--you were tricky with this one. Wrapping your SQL code in a PHP function and posing it as a PHP question was awful slick. This question by itself is, I suppose, fairly relevant to PHP (in spite of its underlying MySQL subject matter)... but the other two are just bizarre and wholly unrelated, to be honest. Just to show I'm not an entirely negative person, I did some searching. After a Google session that lasted all of about a minute and a half, I found this page: http://dev.mysql.com/doc/refman/5.0/en/charset-syntax.html which shows "utf8" being used in a MySQL command. My guess is that answer #1 and answer #3 are "utf8" instead of "utf-8". Todd Boyd Web Programmer -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
