You may want to check "character_set_results" variable through
> SHOW VARIABLES LIKE 'character_set%';
character_set_client utf8
character_set_connection utf8
character_set_database latin1
character_set_filesystem binary
character_set_results utf8
character_set_server latin1
character_set_system utf8
Also, terminal may not be able to display non-latin characters and you may
want to use other clients (GUI clients like MySQL workbench or Navicat,
etc.) to test.
Hope that helps,
Shiva
On Mon, Dec 12, 2011 at 3:30 PM, Jon Forsyth <jon4s...@gmail.com> wrote:
> Hello Michaël,
>
> Thank you for the tips. SHOW CREATE TABLE helped me figure out that my
> table was using Latin1 and I was able to change it to utf-8. However, I
> did not see any encoding specified on the column with this command.
>
> I tried to fix the connection encoding with this line of Perl code:
>
> $dbh->do("SET character_set_client='utf8'");
>
> Now the output is somewhat improved because the arabic is now writing to
> the correct column, but it seems to have an unresolved encoding issue as
> can be seen from a mysql command line query in the token_Arabic column:
>
> +----+--------------+---------+
> | id | token_Arabic | variant |
> +----+--------------+---------+
> | 1 | ?? | yA |
> | 2 | ???? | <bny |
> | 3 | ?? | dA |
> | 4 | ???????? | klmk |
> | 5 | ?????? | Ey$ryn |
> +----+--------------+---------+
>
> Previously this query showed Arabic characters, just in the wrong column.
>
> Thanks,
>
> Jon
>
