[Bug 45475] New: XM6 Type G: Can' t type a specific symbol key on Japanese keyboard.
https://bugs.winehq.org/show_bug.cgi?id=45475 Bug ID: 45475 Summary: XM6 Type G: Can't type a specific symbol key on Japanese keyboard. Product: Wine Version: 3.12 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dinput Assignee: wine-bugs(a)winehq.org Reporter: sagawa.aki+winebugs(a)gmail.com Distribution: --- In XM6 TypeG (SHARP X68000 emulator), I can't type 「:*け」 key with Japanese keyboard. How to reproduce: 1. Download XM6 TypeG version 3.30 L35 from author's page, i.e. http://www.geocities.jp/kugimoto0715/xm6g/xm6_typeg_330L35_20170223.zip (SHA1:ed1b91938ba8ae5f39e1cac9445b8d2740518466) 2. Extract the zip archive. 3. Run xm6g.exe in x86 directory. 4. In the menu bar, choose [ツール] - [オプション] ([Tool] - [Option]). 5. Select キーボード (keyboard) tab. 6. Click No.28 in キーボード マップ (keyboard map) list. Then, a new small window titled 割り当てキーの入力 appears. 7. Type 「:*け」 key on the keyboard. 8. Check the result. To close, click the right mouse button. Expected result: - 現在のキー (Current binding) keeps DIK_COLON. Actual result: - 現在のキー is updated to DIK_APOSTROPHE. About Japanese keyboard specialty in DirectInput, please refer to https://docs.microsoft.com/en-us/previous-versions/windows/desktop/ee416757(...) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45475 --- Comment #1 from Sagawa <sagawa.aki+winebugs(a)gmail.com> --- I'm working on this issue and preparing a patch. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45475 Sagawa <sagawa.aki+winebugs(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download URL| |http://www.geocities.jp/kug | |imoto0715/xm6g/xm6_typeg_33 | |0L35_20170223.zip -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45475 --- Comment #2 from Sagawa <sagawa.aki+winebugs(a)gmail.com> --- I forgot to say you need to obtain iplrom.dat and cgrom.dat (or cgrom.tmp) from somewhere, and put them in the same directory with xm6g.exe before launching it (step 3.). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45475 Sagawa <sagawa.aki+winebugs(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Fixed by SHA1| |6be7d14fb95734528a57abe885c | |60f200d6a071e Resolution|--- |FIXED --- Comment #3 from Sagawa <sagawa.aki+winebugs(a)gmail.com> --- Fixed by 6be7d14fb95734528a57abe885c60f200d6a071e. I'm not sure about mac behavior. If you met something wrong like this issue on macOS, please file another bug report. In my opinion, it requires winemac.drv fix. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45475 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #4 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 3.15. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org