MySQL Bugs: #8040: not complete latin2/cp1250 and collation support

Bug #8040	not complete latin2/cp1250 and collation support
Submitted:	20 Jan 2005 11:12	Modified:	5 Apr 2005 3:11
Reporter:	Stefan Bognar	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	4.1.9	OS:	Windows (windows2000)
Assigned to:		CPU Architecture:	Any

Description:
Hi,

When I tried to use the lastest version of MySQL Server - 4.1.9.
I noticed, that some (not all) of characters are not supported to store in database/table.
I mean some of national characters used in Latin2 or cp1250 codepage.
Collation is bad as well.
I tried everything what was possible to be sure I did nothing wrong.
Only when I set to 'binary' codepage I was able to store full range of east-european characters. But collation didn't work in this case.

How to repeat:
????

Stefan, could you please to give the examples which characters cannot be stored in database and what's wrong with collation? 

If we have repeatable testcase, we will check it and repair.

It's not easy to write here the problem characters, because you may have different
character set in your browser or machine. And they can become distorted or wrong displayed.

But I try to: &#268;,&#269;,&#270;,&#271;,&#356;,&#357;,&#327;,&#328;,&#317;,&#318; (letter c with hiccup, letter C with hiccup, D, d with hiccup, T, t with hiccup, N,n with hiccup, L,l with hiccup) and so on...

I use:
Win 2000 Pro CZ, MyODBC 3.51.10.00,
as a client I tried: VisualFoxPro 6 & Excel (MS Office 2000)

In query result was each problematic character (above mentioned)
substituted with the question mark - ASCII Code 63

Global variables are set:
character_set_client=cp1250
character_set_connection=cp1250
character_set_database=cp1250
character_set_results=cp1250
character_set_server=cp1250

---
But I can read in your manual:
(citation:...10.11.3 Central European Character Sets
We have some support for character sets used in the Czech Republic, Slovakia, Hungary, Romania, Slovenia, Croatia, and Poland......)

So there is probably SOME support for cp1250 characters.
Or not ?

Maybe it is MyOdbc's bug. And mysql is 'innocent'.

But I repeat: When I use 'binary' character set, everything
works great.  I mean all cp1250 or latin2 chracters can be stored
and read-out successfully. Of course without valid collation.

I´m Very very Sorry, If I've been writing wrong things and the BUG is inside me.

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

Could you please attach a picture (using files tab) with the
character when using Excel for example.

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