MySQL docs page should highlight a need of setting up the JIRA db with support of unicode

MySQL integration page at http://www.atlassian.com/software/jira/docs/latest/databases/mysql.html in point 3.1 states:

The URL above assumes a UTF-8 database - ie. created with create database jiradb character set utf8;. If you don't specify character set utf8 you risk getting 'Data truncation: Data too long for column' errors when importing data. See storing non-ASCII characters in MySQL for details.

Although, almost second everyday in SAC there a new case related to the incorrect character encoding used in the JIRA db and characters not supported ASCII or LATIN1 - customers from Asia

I think, this problem originate from our docs, where a "big flashing neon" should print the above quoted instruction. Basically, some users just don't follow the docs page to the letter.