[wp-trac] Re: [WordPress Trac] #3517: WordPress should be 100% UTF-8
WordPress Trac
wp-trac at lists.automattic.com
Wed Jan 31 01:13:14 GMT 2007
#3517: WordPress should be 100% UTF-8
---------------------+------------------------------------------------------
Reporter: sehh | Owner: anonymous
Type: defect | Status: new
Priority: normal | Milestone: 2.2
Component: General | Version: 2.0.5
Severity: major | Resolution:
Keywords: UTF-8 |
---------------------+------------------------------------------------------
Comment (by ryan):
Here's a patch that will SET NAMES and create tables with DEFAULT
CHARACTER SET for new installs running under mysql 4.1 or greater. The
charset and collation are set in wp-config.php as DB_CHARSET and
DB_COLLATE. Old WP installs will not have these defined in their existing
wp-config.php so SET NAMES will not be run. New installs will pick these
values up from wp-config-sample.php. The defaults are utf8 and
utf8_general_ci, but those can be changed. Those upgrading from older WP
versions can set the charset if they like. It is currently up to them to
upgrade their databases to use the new character set. We can look at what
it takes to upgrade old installations. Drupal has some code in the
update_convert_table_utf8() function in
[http://cvs.drupal.org/viewcvs/drupal/drupal/update.php?rev=1.211&view=markup
update.php]. I think there can be some problems doing that in some
scenarios though.
--
Ticket URL: <http://trac.wordpress.org/ticket/3517#comment:10>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list