https://bugs.winehq.org/show_bug.cgi?id=53738
Bug ID: 53738 Summary: Cherry MIDI sequencer cannot read files with a path including CJK characters Product: Wine Version: 7.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: shinichi.tanaka45@gmail.com Distribution: ---
Created attachment 73180 --> https://bugs.winehq.org/attachment.cgi?id=73180 files can be opened (bgm_02.CHY) and cannot be opened (音楽_02.CHY). these files are same except its filename.
A MIDI sequencer application "Cherry" (http://hp.vector.co.jp/authors/VA010012/, its UI is in Japanese because of Japanese developer) cannot open some files with a path including CKJ characters.
When trying to open a file with CJK path, the app Cherry shows a dialog "File reading error or a malformed file format" (in Japanese). When launch in terminal with like "wine cherry.exe" then reproduce that behavior, but this app does ntnot output any logs about that.
Detailed situations are like this:
- files with a name only with ASCII characters can be opened - files with a name including CJK characters cannot be opened - files with a name only with ASCII but in a directory with CJK characters cannot be opened
These behaviors are reproduced in all published versions of Cherry in that website :
- v1.4.3 - v1.5.2 (alpha) - v1.5.3 (alpha)
And the locale info in my machine is here:
``` locale LANG=ja_JP.UTF-8 LANGUAGE=ja:en_US:en LC_CTYPE="ja_JP.UTF-8" LC_NUMERIC=ja_JP.UTF-8 LC_TIME=ja_JP.UTF-8 LC_COLLATE=en_US.UTF-8 LC_MONETARY=ja_JP.UTF-8 LC_MESSAGES="ja_JP.UTF-8" LC_PAPER=ja_JP.UTF-8 LC_NAME=ja_JP.UTF-8 LC_ADDRESS=ja_JP.UTF-8 LC_TELEPHONE=ja_JP.UTF-8 LC_MEASUREMENT=ja_JP.UTF-8 LC_IDENTIFICATION=ja_JP.UTF-8 LC_ALL= ```
I tried some launching way below with specifying locale but these behaviors are reproduced:
- `LC_ALL=ja_JP.UTF-8 wine cherry.exe` and open CJK path files - `LANG=ja_JP.UTF-8 wine cherry.exe` and open CJK path files
I feel this may not be a problem about WineHQ, may be simply a problem about my locale settings, but I cannot resolve this so report as a bug.