MySQL Bugs: #14570: can not execute or display SQL with Chinese character well

Bug #14570	can not execute or display SQL with Chinese character well
Submitted:	2 Nov 2005 11:31	Modified:	20 Dec 2005 9:42
Reporter:	Bear Xu	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S3 (Non-critical)
Version:	1.1.17	OS:	Windows (Windows 2003)
Assigned to:		CPU Architecture:	Any

Description:
I use MySQL Query Browser 1.1.17 
After I set the fonts in options dialog, 
it can display Chinese character, but not good. the character seems very narrow . and there is a "Range check error". 

If you paste some text with Chinese to the Code memo, 
the code memo will be dead, you can not edit it, 
and you can not execute the SQL in code memo. 

See the screenshot: (the Chinese characters are "中国支持") 
http://www.wordhacker.com/temp/MQB_Chinese.JPG 

The sql code memo is not a native windows memo? 

I think the SQL code MEMO should support unicode by default as that in Windows. 

Bear

How to repeat:
If you paste some SQL text with Chinese to the Code Memo, 
then execute

 CREATE TABLE Books (
  id INT UNSIGNED AUTO_INCREMENT NOT NULL PRIMARY KEY,
   title VARCHAR(200),
   body TEXT,
   FULLTEXT (title,body)

INSERT INTO Books (title,body) VALUES
('MySQL权威指南','作为一种开源数据库')

SELECT * FROM Books
WHERE MATCH (title,body) AGAINST ('数据库');

Suggested fix:
Code memo should support unicode

Please increase the "Width" setting for the Code Font to 15 or higher in the option dialog. Then you should be able to read all letters.

After setting the width as 15, the code memo still has problem:

It is out of control, can not show characters correctly, 
can not clear, have to use Ctrl+A to clear, very strange.

I'm waitting!

I was not able to reproduce the bug. I pasted your code in code memo and I did't find any problems. But I found if I set width to 17 and re-start Query Browser, Query Browser "forgets" to set width correctly in code memo. Do you have same problem ?

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