Page 1 of 1

suggested improvements for korean simplified keyboard

Posted: Mon Oct 17, 2011 2:39 pm
by juniecho
with simplified korean keyboard("단모음 키보드") it is often necessary to pause typing and wait for a few seconds to ensure that last consonant will not affect the next letter.

for example when i try to type "학교" (school), without pausing it becomes "하꾜" since the last consonant is same "ㄱ" with the fist consonant of the next letter "교". (the last "ㄱ" becomes double consonant of the next letter)

this seriously affects the performance of the simplified korean keyboard and needs to be fixed. but on the other hand, this behavior is very often necessary since there are a lot of words that need double consonants.

i suggest changing the COMMA key which is just left to the spacebar to BREAK key (to finish the last letter and force move). commas can be entered by long pressing the period key and therefore is rebundent.

i will post the same thing in korean language in order to make it more clear to your korean keyboard developer, in case you have any.

Re: suggested improvements for korean simplified keyboard

Posted: Mon Oct 17, 2011 2:47 pm
by juniecho
단모음 키보드를 사용할 때는 가끔씩 타이핑을 일부러 잠시 쉬어야 할 때가 있습니다. 예를 들면 학교 등의 단어를 입력할 때, 교 자가 바로 전의 학 자의 마지막 자음인 ㄱ의 영향을 받아 쌍자음으로 입력되어 꾜 자가 되는 것을 방지하려면 타이핑을 잠시 쉬어야 합니다.

빠른 시간에 자음을 두번 연타하면 쌍자음이 되는 동작은 당연히 필요합니다만 동시에 단모음 키보드의 입력속도를 크게 저하시키는 주범입니다. 따라서 일부 개선할 필요가 있습니다.

스페이스 바 왼쪽에는 쉼표 키가 있는데, 쉼표는 이미 스페이스 바 오른쪽의 마침표 키를 길게 눌러서 입력할 수 있으므로 별도의 쉼표 키를 굳이 둘 필요가 없습니다.

따라서 쉼표 키를 삭제하고, 현재 입력중인 글자의 입력을 강제로 완결하고 다음 글자를 입력할 수 있게 끊는 키를 그 자리에 넣는 것이 좋지 않을까 합니다.

Re: suggested improvements for korean simplified keyboard

Posted: Mon Oct 17, 2011 4:47 pm
by harshlad
U need to touch the space key before inputing secondary 'ㄱ'.
If you want to type '학교', touch 'ㅎ', 'ㅏ', 'ㄱ', [Space], [BackSpace], 'ㄱ', 'ㅛ' sequentially with no delay. That's all okay.

Re: suggested improvements for korean simplified keyboard

Posted: Mon Oct 17, 2011 4:59 pm
by juniecho
oh i'm already well aware of hitting spacebar and then backspace, which involves two keypresses.
when it comes to some serious messaging that's too much, due to the actual distance between spacebar and backspace.

some other simplied korean keyboard software called "hybrid keyboard" already has this feature.
(package name is "kr.android.hybridkey". see https://market.android.com/details?id=k ... .hybridkey.)

Re: suggested improvements for korean simplified keyboard

Posted: Tue Oct 18, 2011 6:16 am
by harshlad
Hm... The best is, 'Artificial Intelligence.' as you know.
For example, ㅎ,ㅏ,ㄱ,ㄱ,ㅛ(sequantial) should be recognized that ㄱ after ㄱ is separated character because of following character is 'ㅛ'. ( '학 교' )
Hangul consists of 14 consonants and 10 vowels, and it contains some principle to locate those at right place.

I want for smart keyboard app to know the principle of arranging Korean characters.
Then U don't need to press 'fixing' key.

Re: suggested improvements for korean simplified keyboard

Posted: Tue Oct 18, 2011 8:19 am
by juniecho
yes the best would be automatic recognition, but considering the vast number of korean words and there is no principle (i'm a native korean - in fact there are some principles but also a lot of exceptions, so we will have to take care of all of those to make a 'working' ai.) the best bet is dictionary based approach instead of ai.

"google korean keyboard" takes this dictionary based approach and it is fairly working well, but not very accurate all times. this is mainly because in korean there are a lot of words or sentence structures that require more complex processing by the ai. for example, past tense sentence in honorific require double consonant and same consonant following with the next letter (ㅆ+습) which involves triple pressing of "ㅅ". things like this critically reduces the effeciency of korean simplified keyboard. (i was quite annoyed by the google keyboard due to its poor dictionary handling)

when ai is good enough it is clearly better to use the ai, but in korean simplied keyboard it would be extremely hard to code such a 'fairly working' ai. so until we can think of more reliable algorithm to handle this it is better to leave the decision to the user by having a break key i think.


oh, by the way, the function of the break key is simple. it just automates what you mentioned earlier - spacebar and backspace - in one keypress.