MySQL Bugs: #17489: Problem with Extended characters not transferring properly

Bug #17489	Problem with Extended characters not transferring properly
Submitted:	16 Feb 2006 18:45	Modified:	9 Jun 2006 16:33
Reporter:	Andrzej Imiolek	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Migration Toolkit	Severity:	S2 (Serious)
Version:	1.0.23	OS:	Windows (Windows 2003 SP1)
Assigned to:	Michael G. Zinner	CPU Architecture:	Any

Description:
When a source field contains the trademark extendeded character (™), it is imported as a question mark into MySQL.  

How to repeat:
The source database is MS SQL 2000.  Source database has a character set of "Latin1".
The source column is of type "Varchar(50)" and contains "PRO™".  

The destination database is MySQL 5.0.18.  I have tried this using character sets of both Latin1 and UTF-8 on the destination table, with the same result.  

When the migration tool moves the data, it appears as "PRO?".

Manually changing the Question mark to the ™ character (editing the field in the resultset of Query Browser) in MySQL works , but even then it does not display properly in the Query Browser Resultset (looks like a double wide subscripted pipe character).

Suggested fix:
All Latin1 characters should remain the same after being imported into a table with a character set of Latin1.

Thank you for the bug report. I tried also with Object Mapping
Multilanguage options.

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html