Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Japanese IME and Korean Input do not work on Windows #802

Closed
MuffinTastic opened this issue Jan 18, 2019 · 5 comments · Fixed by #924
Closed

Japanese IME and Korean Input do not work on Windows #802

MuffinTastic opened this issue Jan 18, 2019 · 5 comments · Fixed by #924
Labels
bug some feature is broken OS-Specific: Windows
Milestone

Comments

@MuffinTastic
Copy link

Tested on Windows 8.1 and in a Windows 10 VM. Strangely enough, (Simplified) Chinese IME works.

I am not quite familiar enough with Korean input to say what should generally happen, but none of the input makes it through.

Expected functionality for JP IME would be:
Type the romanized text, and while you're typing, the text changes to its hiragana equivalent (or otherwise depending on IME mode) in real time, appearing with an underline beneath it. Arrow keys Up/Down or [Shift+]Tab allow you to choose suggestions for the whole of the text, or if you press space, you can change individual parts of the text into the IME's suggestions via Left/Right, and Up/Down or [Shift+]Tab. After you hit Enter, the underlined text is inputted into the field and the underline goes away.

What actually happens is... nothing. The IME doesn't work, the game just eats all of the input, even the ASCII characters. Typing as though the IME were working doesn't work.

Seeing as the IME doesn't work, I'm unsure as to whether or not there are UI elements displaying the IME's suggestions. If not, that's another thing to look into.

Typing the text in another program and pasting it into OpenSpades does work, but this is obviously not ideal.

@yvt yvt added bug some feature is broken OS-Specific: Windows labels Jan 19, 2019
@yvt
Copy link
Owner

yvt commented Jan 19, 2019

Updating SDL2.dll to the latest version (x86) seemed to fix the issue on my side. Can you try it on your machine and see if it works?

@MuffinTastic
Copy link
Author

MuffinTastic commented Jan 20, 2019

yeah, that works, on both 8.1 & 10

@feikname
Copy link
Collaborator

feikname commented Jun 4, 2019

@yvt is the SDL2.dll bundled in latest OpenSpades version enough to close this issue?

@yvt
Copy link
Owner

yvt commented Jun 4, 2019

@feikname Can’t test it right now, but I don’t think so. I’ll close the issue when the external library package is updated to include the latest version of SDL2.dll.

@yvt yvt added this to the 0.1.4 milestone Jul 15, 2019
@yvt yvt mentioned this issue Nov 21, 2019
@Conticop
Copy link

Seems like updating SDL2 would fix 3/4 (or even more) different issues at once lmao.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug some feature is broken OS-Specific: Windows
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants