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

Pressing ' conflicts with Korean keyboard composition #2203

Closed
soomtong opened this issue Jul 2, 2019 · 2 comments · Fixed by #2204
Closed

Pressing ' conflicts with Korean keyboard composition #2203

soomtong opened this issue Jul 2, 2019 · 2 comments · Fixed by #2204

Comments

@soomtong
Copy link

soomtong commented Jul 2, 2019

in korea some use not typical keyboard layouts like me.
common korean word made by automatas that state seleted mode
in this case, some key use ' for typo, not a quote.

see this image

auto-quotes

we want to disable this automatically quite feature.
but can't see disable option.

Example URL:

@fregante fregante changed the title disable auto quite that selected text around Pressing ` conflicts with Korean keyboard composition Jul 3, 2019
@fregante fregante changed the title Pressing ` conflicts with Korean keyboard composition Pressing ' conflicts with Korean keyboard composition Jul 3, 2019
@fregante fregante self-assigned this Jul 3, 2019
@fregante
Copy link
Member

fregante commented Jul 3, 2019

Are you using Windows? I can't replicate that behavior on macOS

오빠

@soomtong
Copy link
Author

soomtong commented Jul 3, 2019

in korean typically use standard type layout, that korean characters not use special key like quote, question... it likes qwerty layout.
but someone use another layout. it needs more keys for each korean characters.
normally non-korean can't reproduce this situation i think.
as u see I saw fix-composing-events patch and confirm it solved.
so we can close this issue and relates.
and u may know I am happy with refined-github more!

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

Successfully merging a pull request may close this issue.

2 participants