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

Reporting of IME opened/closed undesirable for most languages #2687

Closed
nvaccessAuto opened this issue Sep 26, 2012 · 5 comments
Closed

Reporting of IME opened/closed undesirable for most languages #2687

nvaccessAuto opened this issue Sep 26, 2012 · 5 comments

Comments

@nvaccessAuto
Copy link

Reported by nvdakor on 2012-09-26 09:28
Hi,
When switching languages between ones which uses IME and those which doesn't (such as between English and Korean), outputting IME opened/closed messages could be too verbose for users. At least Korean users prefer that this message should be turned off.

@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2012-09-27 01:58
I believe this was implemented for Japanese, where I assume there's some way to toggle IME open/closed without actually changing language.

Are you saying that for Korean, you hear IME open/closed even when you switch to a completely different layout? For clarity, please provide exact steps to reproduce, including the exact names of the keyboard layouts you're using.

@nvaccessAuto
Copy link
Author

Comment 2 by jteh on 2012-09-27 05:54
Changes:
Changed title from "IME opened/cosed: these are not needed, as it could be verbose" to "Reporting of IME opened/closed undesirable for most languages"
Milestone changed from None to 2012.3

@nvaccessAuto
Copy link
Author

Comment 3 by nvdakor on 2012-09-27 16:51
Hi,
I'm using Korean IME and English U.S. keyboard layout. In my case, to swich languages, one would press right alt with shift key. Before, I would hear just native input and alphanumeric input; however, with the latest version, I hear "IME opened, native input" and "IME closed, alphanumeric input". Many Korean users prefer the former approach. Thanks.

@nvaccessAuto
Copy link
Author

Comment 4 by mdcurran on 2012-10-03 01:48
Fixed in 72d0e41.
Changes:
State: closed

@nvaccessAuto
Copy link
Author

Comment 5 by mdcurran on 2012-10-03 01:48
Sorry, fixed in 439fc42.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants