After living in Japan for six years and doing web programming for most of that time, you would think I would have this down by now. I used many combos – from Lasso/FileMaker to PHP/MSSQL and even PHP/PostgreSQL – but never used PHP/MySQL for any CJVK work. So I did some Googling and found four pages that claimed to have the answer:
- Use UTF-8 No BOM for each page. That is Byte-Order Mark, which does help in other languages like Cold Fusion, but not for me in PHP. NOPE!
- Use a PHP header tag:
header('Content-Type: text/html; charset=utf-8');
and use a HTML meta tag:
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- Use SET NAMES ‘utf8′; when instantiating your database object. NOPE!
- Change the column to utf8_general_ci and the collation to utf8_general_ci. NOPE!
I saw that PhpMyAdmin was displaying the characters correctly, so how were they doing it? I did a deep dive into the code and wound up at the mysql dbi connector where the following statements were set for EVERY query:
mysqliObj->query("SET CHARACTER SET 'utf8'"); mysqliObj->query("SET collation_connection = 'utf8_general_ci'");
This, along with the column set to utf8_general_ci did the trick. The processing pages were set to Western (Mac OS Roman) which did not cause any problems inserting or displaying Japanese data.
This post is more for myself so I don’t ever forget how this is done. This can be black magic sometimes so I need some documentation.
Hey, like this post? Why not share it with a buddy?Tweet