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

Input Method has issues with composing Korean characters #2968

Closed
Myriads opened this Issue Nov 19, 2014 · 2 comments

Comments

Projects
None yet
2 participants
@Myriads

Myriads commented Nov 19, 2014

This issue was closed but these problems are still existed in IM part of Processing. So I reopen it.
->
There are 2 bugs to use Korean characters:

If any ASCII character such as white space, comma, dot, or number is typed in during composing the Korean character, the currently composed Korean character is disappeared in the screen of the Edit .

Korean characters are commonly consisted of 3 components: 1) beginning consonant, 2) vowel, and 3) final consonant. Sometimes the final consonant of the previous composed character becomes the beginning consonant of the following composed character. If the previous final consonant becomes the beginning consonant of the next composed character, then the previous composed Korean character should be redrawed with the final completely composed Korean character, but it is still displayed with the final consonant which becomes the beginning consonant of the next Korean character.

@benfry benfry added the help wanted label Nov 19, 2014

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Nov 19, 2014

Member

The syntax.im code was contributed and we have no one with experience in this area, so we'll need help on this one.

Member

benfry commented Nov 19, 2014

The syntax.im code was contributed and we have no one with experience in this area, so we'll need help on this one.

@benfry benfry changed the title from Input Method to compose complex characters to Input Method has issues with composing Korean characters Nov 19, 2014

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Feb 14, 2016

Member

Closed with #4293 for 3.0.2.

Member

benfry commented Feb 14, 2016

Closed with #4293 for 3.0.2.

@benfry benfry closed this Feb 14, 2016

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