MySQL Bugs: #35535: Columns with "charset" = utf8 don't display unicode characters correctly.

Bug #35535	Columns with "charset" = utf8 don't display unicode characters correctly.
Submitted:	24 Mar 2008 19:10	Modified:	8 May 2008 23:42
Reporter:	Jim Knepley	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S3 (Non-critical)
Version:	1.2.12	OS:	Windows (XP SP2)
Assigned to:		CPU Architecture:	Any
Tags:	Unicode, utf8

Description:
In a table that looks like this:
+----------+---------------------+-----------------+------+
| Field    | Type                | Collation       | Null |
+----------+---------------------+-----------------+------+
| id       | int(10) unsigned    | NULL            | NO   |
| address  | varchar(255)        | utf8_general_ci | YES  |
| accuracy | tinyint(3) unsigned | NULL            | NO   |
+----------+---------------------+-----------------+------+

Where "address" is set to use a "column charset" of utf8, and the default table character set is utf8, unicode strings stored in the "address" column are not decoded and displayed correctly when they are part of a query result.

How to repeat:
Insert data in the "address" column with unicode characters, such as these international address examples:

25, Avenue André Prothin, 92400 Courbevoie, France
Gradestraße 30, 12347 Britz, Berlin, Germany
Rüsselsheimer Straße 34, 60326 Gallusviertel, Frankfurt am Main, Germany
Süderstraße 315, 20537 Hammerbrook, Hamburg, Germany

...and use Query Browser to select that data. The unicode isn't decoded. The same query in the MySQL CLI outputs as expected.

Suggested fix:
Make the results grid aware of the character encoding in each colum, and decode those characters as appropriate.

Thank you for the bug report. Could you please provide a dump file of the
table with some insert data which shows the behavior reported. Thanks in
advance.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".