------_=_NextPart_001_01C58BC7.8ECEAEE0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello everyone.

I got MySQL version 5.0.9 Beta, mysql++ 2.0 Beta and using VS.NET 2003 =
(Ver. 7.1), Windows XP Pro

=20

I am having issues with Unicode characters.

All the examples of mysql++ compiled and ran fine.

I even got the from the stock table:

=20

N=FCrnberger Brats 92 1.5 8.79 2005-03-10

=20

And they are shown just fine as well, but Russian and Chinese do not =
show up, they are shown as "????????"

I used the utf8_to_win32_ansi function and I comented out the section =
where it converts strings back.

However they do show up in MySQL Query Browser,

=20

It was working in MySQL 5.0.3 Beta and in mysql++ 1.7.35 before, but I =
was not paying attention where it stopped working prior to the very last =
versions of mysql++ and MySQL 5.0.9

=20

Any idea where the bug could be? I couldn't find this issue on the bug =
list in MySQL.

=20

Thank you for your help.

=20

Tim Shor

timsho (AT) parlec (DOT) com <mailto:timsho (AT) parlec (DOT) com>=20

=20


------_=_NextPart_001_01C58BC7.8ECEAEE0--

Tim Shor wrote:

Do you mean they don't show up in a console mode program? If so, of
course they don't. They're not in Latin-1. Read the Unicode chapter
in the user manual:

http://tangentsoft.net/mysql++/doc/u...l/unicode.html

If you mean some other output device, which one? Can you make Russian
or Chinese characters show up on it without sending them through MySQL++?

utf8_to_win32_ansi() doesn't revert any conversions. It makes two
conversions, so there are three different character spaces involved:
UTF-8, UCS-2, and ISO 8859-1 (Latin-1). There is no "back", so I don't
know what you are talking about.

All the past versions of MySQL++ are available from the web site (if you
can't figure out their URLs, you have no business being a programmer) or
in the Subversion repository.

https://gna.org/svn/?group=mysqlpp

If you find a regression, it's then trivial to pinpoint where the change
occurred, with a binary search through the revision tree.

Help me help you.

--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe: http://lists.mysql.com/plusplus?unsu...ie.nctu.edu.tw

1. Sorry, it is in GUI using Windows.Forms, also in debugging they show
up as "???" marks.

2. I am able to see Russian and Chinese characters in the UIs and within
debugging without going through mysql++ and MySQL

Thank you for your help.

Tim Shor



--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe: http://lists.mysql.com/plusplus?unsu...ie.nctu.edu.tw

Please localize the version of MySQL or MySQL++ that caused the regression.

--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe: http://lists.mysql.com/plusplus?unsu...ie.nctu.edu.tw

Hello every one.
Well, I got to the bottom of it, in some way.
1. I am using MySQL Server 5.0.9 and currently my default storage is =
innoDB with the default character set utf8.
2. I also use MySQL Query Browser 1.13 through which I populate my test =
database with Chinese characters. When I insert a record within Query =
Browser I can see Chinese characters in this GUI tool.

3. In mysql++ 2.0.0 and all the versions (1.7.32, 1.7.35, 1.7.40) when I =
execute the examples with stock table everything runs fine.
Now, when I launch Query Browser and do "select * from stock" I get the =
following:
'N=C3=BCrnberger Brats', 92, 1.5, 8.79, '2005-03-10'

Instead of:
'N=FCrnberger Brats', 92, 1.5, 8.79, '2005-03-10'

4. When I insert records from Windows application using mysql++ api that =
contain Unicode characters they are not displayed properly in MySQL =
Browser, but will look just fine when I query the database via mysql++ =
and transform them from UTF8 to UCS2. And when I insert Unicode =
characters into the database using MySQL Browser they look just fine =
within MySQL Browser, but when I query that table using mysql++ with =
utf8_to_ansi conversion mechanism, my data looks like this: "????????".
So the bottom line, what is going on? Is it a bug, then where is it in =
MySQL, MySQL Query Browser, MySQL++, or in my brain?

Thank you for your input and feedback.

Timofey Shor
timsho (AT) parlec (DOT) com
-----Original Message-----
From: Warren Young [mailto:mysqlpp (AT) etr-usa (DOT) com]=20
Sent: Monday, July 18, 2005 5:16 PM
To: MySQL++ Mailing List
Subject: Re: Unicode Characters

Please localize the version of MySQL or MySQL++ that caused the =
regression.

--=20
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe: =
http://lists.mysql.com/plusplus?unsu...rlec (DOT) com


--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe: http://lists.mysql.com/plusplus?unsu...ie.nctu.edu.tw