Bug #22659 About multibyte charactor display problem in Query Browser
Submitted: 25 Sep 2006 9:56 Modified: 28 Oct 2006 8:38
Reporter: Wei Zhi Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Query Browser Severity:S3 (Non-critical)
Version:1.2.3Beta OS:Windows (Windows XP Professional)
Assigned to: CPU Architecture:Any
Tags: Multibyte Character

[25 Sep 2006 9:56] Wei Zhi
Description:
In Code area,I found multibyte string can't be displayed properly.

In Option dialogue I found a config option to change application fonts,here I can change the code font.But as you know,single byte character and multibyte character has different width,when I change the width to fit the multibyte character the English characters' distance are to far,reverse operation makes I can't see the whole character of multibyte language.

Speak truthfully, this tool has ugly support for multibyte language characters.Hope your hardworking developing can fix this soon.

How to repeat:
Every time.
[25 Sep 2006 13:31] Tonci Grgin
Hi Zhi and thanks for your problem report. MySQL GUI tools are work in progress and with hard task of running/looking the same on many platforms...

I would like to change synopsis to "MySQL GUI tools not properly scaling controls when used with monospaced/multibyte fonts". Do you agree?

Please attach a snapshot of your screen that's troubling you and font settings.
[27 Sep 2006 3:11] Wei Zhi
Screen1

Attachment: p1.png (image/png, text), 9.66 KiB.

[27 Sep 2006 3:12] Wei Zhi
Screen2

Attachment: p2.png (image/png, text), 9.66 KiB.

[27 Sep 2006 3:15] Wei Zhi
Hi,Tonci:

I Uploaded two screen snapshot,one is width,one is narrow.
[28 Sep 2006 8:38] Tonci Grgin
Hi Zhi.
Did you check which fonts you use, ie. which font would be proper variable-width font on your system working in other applications?
[28 Oct 2006 23:00] Bugs System
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".