怎么让mysql支持全球语言_转换mysql数据库以支持多种语言

I'd go for it. There are very few reasons not to go with utf8 when working with multiple languages.

The table character set and collation are used as default values for column definitions if the column character set and collation are not specified in individual column definitions.

If you don't have individual collations/character sets on fields, you can write a simple scripts that loops through all tables and issues ALTER TABLE tablename CONVERT TO CHARSET utf8;. If your fields have custom character sets/collations, you'll have to issue a MODIFY COLUMN statement. You can easily identify those querying the information_schema.columns table after your conversion.

Yes, if data cannot be represented in utf8 (which is unlikely given your current collation), data can break. Also, if you stored utf8 text in columns which weren't actually utf8, converting those fields results in something like a double utf8-encoding, which is a pretty inconvenient mess to clean up. If you know a column to be wrongly used to story utf8, you can convert it to bin & then to utf8 to prevent conversion/double encoding.