| Bug #49593 | no proper unicode support | ||
|---|---|---|---|
| Submitted: | 10 Dec 2009 16:24 | Modified: | 26 Feb 2010 21:41 |
| Reporter: | Peter Laursen (Basic Quality Contributor) | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
| Version: | 5.2.10 | OS: | Windows (win7 - 64 bit) |
| Assigned to: | Alfredo Kojima | CPU Architecture: | Any |
| Tags: | qc | ||
[10 Dec 2009 16:24]
Peter Laursen
[10 Dec 2009 16:26]
Peter Laursen
Danish 'æ' garbled in log viewer.
Attachment: unicode.jpg (image/jpeg, text), 21.85 KiB.
[10 Dec 2009 16:45]
Peter Laursen
One more example from bug49592 where 'ø' garbles Der k�rer allerede en udgave af tjenesten. (= an instance of this service is already running)
[10 Dec 2009 18:13]
Peter Laursen
Maybe it is rather 'no proper non-unicode support'? :-) It looks like WB expects characters outside ASCII-range returned by the OS to be UTF8-encoded here (ie. does not recognize ANSI codepages). This is cosmetical only with Danish etc. of course. Anyway it could be interesting to see with a Windows localization not using latin script (like Japanese).
[14 Dec 2009 13:44]
Susanne Ebrecht
Many thanks for writing a bug report. This could be server related. Anyway, we will look if we are able to repair it.
[14 Dec 2009 13:49]
Peter Laursen
I do not understand 'server related'. The messages are returned from the Windows Service Manager. It should be simple to try this on a Russian or Japanese system for instance. Is it possible to understand the output on such systems?
[30 Dec 2009 20:06]
Alfredo Kojima
Changed version to 5.2.10, I assume this was a typo. Problem is unrelated to server, it just needs to convert from "native" codepage to UTF8 when displaying Windows system messages.
[30 Dec 2009 20:16]
Peter Laursen
Yes .. version was a typo. Thanks for correcting! .. and yes .. to use C-typology, the Windows messages will need to be cast from BYTE to MULTIBYTE string before displaying if this console window assumes utf8, what it looks like it does (I do not think Windows will ever return 'Windows unicode' (WIDECHAR) in such messages - only ANSI (BYTE) data will probably occur). But not sure about CJK-localisations.
[31 Dec 2009 1:36]
Alfredo Kojima
Character set detection and conversion added for Windows
[26 Jan 2010 21:41]
Johannes Taxacher
Hi Peter, could you try this with 5.2.14 again to see if this works out for you as well?
[27 Feb 2010 0: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".
