Bug #5566 MySQL doesn't start if installed in path containing Unicode characters
Submitted: 14 Sep 2004 11:33 Modified: 7 May 2005 10:20
Reporter: Alexander Keremidarski
Status: Duplicate
Category:Server Severity:S2 (Serious)
Version:4.1.4 OS:Microsoft Windows (Windows)
Assigned to: Alexander Barkov Target Version:

[14 Sep 2004 11:33] Alexander Keremidarski 
Description:
When MySQL is intalled under a path containing unicode characters (e.g. japanese) it
fails to start with message

"Can't find message file 'C:\???\share\english\errmsg.txt'". 

How to repeat:
Install MySQL under directory with international characters.
[17 Sep 2004 0:08] Jorge del Conde 
I wasn't able to repeat this using 4.1.4

I installed mysql in the following path:

c:\míñá\mysql\
[27 Oct 2004 3:04] Lachlan Mulcahy 
Unable to repeat with 4.1.4-gamma on Windows 2000 with all the latest service packs.

Installed into c:\myésql\ and was able to start server and connect fine.
[27 Oct 2004 13:33] Alexander Keremidarski 
The bug does not affect *ALL* unicode characters.

It happens with concrete japanese characters only.
[31 Dec 2004 1:57] Miguel Solorzano 
MySQL Starts on Japanase Windows

Attachment: japan1.PNG (image/png, text), 21.86 KiB.
[31 Dec 2004 2:00] Miguel Solorzano 
I tested the server 4.1.8 on Windows 2000 Japanese version with
a path with Japanese characters (please look the picture attached to
this bug report - Files tab).
[5 May 2005 14:24] Jim Winstead 
Resetting to 'Open'.

This probably happens with filenames where the second-byte of a Shift-JIS character is
0x5c -- which is a '\'. This likely then gets corrupted in the directory-munging
functions like clean_dirname().
[5 May 2005 14:36] Miguel Solorzano 
Jim,
Yes you are right. I did the test with those characters testing another
customer issue and I forgot to edit this bug. Thanks.
[7 May 2005 10:20] Alexander Barkov 
Duplicate with 3906