MySQL Bugs: #7925: latin2->latin1 conversion is incorrect

Bug #7925	latin2->latin1 conversion is incorrect
Submitted:	15 Jan 2005 11:35	Modified:	21 Jan 2005 11:09
Reporter:	Martin Devera	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	4.1.9	OS:	Linux (Linux 2.4.9, glibc 2.3.2)
Assigned to:	Alexander Barkov	CPU Architecture:	Any

Description:
It seems that the server incorrectly translates from latin2 table column into latin1 connection charset. Server compiled default charset is cp1250. See http://luxik.cdi.cz/~devik/files/mysqlchar.gif. There is table test with column a defined as character set latin2 and table is filled with correct latin2 text.
With "set names latin2" the "select a from test" is ok. With "set names latin1" the same select displays <9A>e?ik. The ? is ok because R with carron is not in latin1. But <9A> is bad - S with carron is not in latin1 too thus ? should be there too.
Probably it is not incidental that <9A> is S with carron's code in cp1250 which is server's default set. Just for information:
mysql> show variables like 'character_set\_%';
+--------------------------+--------+
| Variable_name            | Value  |
+--------------------------+--------+
| character_set_client     | latin1 |
| character_set_connection | latin1 |
| character_set_database   | cp1250 |
| character_set_results    | latin1 |
| character_set_server     | cp1250 |
| character_set_system     | utf8   |
+--------------------------+--------+

It seems as if column's latin2 => connection latin1 is done via cp1250 or what ....

How to repeat:
See description above.

Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.mysql.com/documentation/ and the instructions on
how to report a bug at http://bugs.mysql.com/how-to-report.php

Additional info:

This is not a bug. Your terminal is running in latin2 mode.
It cannot display both latin2 and latin1 correctly at the 
same time.