MySQL Bugs: #21340: Turkish character problem

Bug #21340	Turkish character problem
Submitted:	29 Jul 2006 13:59	Modified:	10 Sep 2006 13:10
Reporter:	Harun ÇAKMAKÇI	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	Connector / NET	Severity:	S2 (Serious)
Version:	1.0.7	OS:	Windows (Windows XP)
Assigned to:		CPU Architecture:	Any

Description:
the bug with 16748 ID number which have been reported before is not solved yet.
The mysql connector 1.0.7 still have errors to display turkish characters.

How to repeat:
harunc@gmail.com

the bug with 16748 ID number which have been reported before is not solved yet.
The mysql connector 1.0.7 still have errors to display turkish characters.

Hi Harun and thanks for your problem report. The bug you are reffering to is closed by reporter as solved.
Can you please post all relevant data. For example, I would like to see the result of your SHOW VARIABLES LIKE "%char%" command.

result of my SHOW VARIABLES LIKE is 
character_set_client     | latin1
character_set_connection | latin1
character_set_database   | latin1
character_set_filesystem | binary
character_set_results    | latin1
character_set_server     | latin1
character_set_system     | utf8
character_sets_dir       | /usr/share/mysql/charsets/.

I know this is not Turkish character set but I when use another connector for .NET(not changing any variables)  the display of turkish character is correct .

Harun, please read http://bugs.mysql.com/how-to-report.php carefully and provide as much data as possible. 
I know for a fact NET connector has no problems with Hebrew characters so I dare to say there's no problem with Turkish too.
Did you put charset=xxx; into your connection string? Are all the labels/text-boxes in your application set to right charset? What is the MySQL server version you're using?...
Please post SQL script containing data needed to repeat this problem as well as small project demonstrating it, preferably C#.

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".