21 messages over 3 pages: 1 2 3 Next >>
IronFist Senior Member United States Joined 6438 days ago 663 posts - 941 votes Speaks: English* Studies: Japanese, Korean
| Message 1 of 21 06 February 2010 at 10:25pm | IP Logged |
You know how with Japanese, there are two ways to type it:
1. You can learn the layout of a hiragana keyboard (no thanks)
or
2. You can type in romaji and it changes it to hiragana (yes please!)
Is there an equivalent of #2 above for Korean?
I've only seen Korean programs that allow you to type by memorizing the hangul layout of each keyboard. I'm sure that's a wonderful skill to learn over time, but I don't really want to do that right now.
So if #2 doesn't exist, does anyone know anyone who could program it? I have logically figured out exactly how it would work, I just lack the programming and system knowledge to actually implement it.
I'm totally serious. This could be huge. Everyone uses the romaji Japanese keyboard programs... think about it, the Korean program that we create could become equally as popular.
1 person has voted this message useful
| Warp3 Senior Member United States forum_posts.asp?TID= Joined 5536 days ago 1419 posts - 1766 votes Speaks: English* Studies: Spanish, Korean, Japanese
| Message 2 of 21 06 February 2010 at 11:37pm | IP Logged |
The problem with Korean is that it isn't as easily romanized as Japanese due to the more complex phonetic system in Korean, which is partly why so many highly varied romanization systems exist for Korean (and the ones that romanize the most accurately would also be the worst candidates for a romanized input system since the letters used change on the fly to match the sound shifts in Korean).
Honestly, though, in my opinion, it doesn't take that long to learn the Hangul keyboard (I was actually surprised at how soon I was able to turn off the on-screen keyboard, which I had been using for visual reference to remember where each key was initially) and the typing speed is quite good with this layout since the consonants and vowels are mapped to different ends of the keyboard (so you alternate hands much more than typing in English).
In addition, a big part of the reason that the romanization input systems exist for Chinese and Japanese is because they use ideographs (Hanzi/Kanji) heavily (or in the case of Chinese, exclusively) and there isn't really a good way to "type" an ideograph. Korean has an alphabet, though, which only has a few more characters total than the English alphabet and the extras are easily mapped to SHIFTed letters since Korean doesn't use capitalization. The SHIFTed consonants are easy to remember as they are all the "tensed" versions of the normal consonants (i.e. SHIFT + ㅅ = ㅆ) and there are only two SHIFTed vowels which are both y + vowel versions of the non-SHIFTed character on that key.
I'm not saying that a romanized input system for Korean wouldn't be popular (I'm sure it would be), just that I personally don't see the need for it with Korean given it's differences with the other languages that have that feature.
Edited by Warp3 on 06 February 2010 at 11:40pm
1 person has voted this message useful
| IronFist Senior Member United States Joined 6438 days ago 663 posts - 941 votes Speaks: English* Studies: Japanese, Korean
| Message 3 of 21 07 February 2010 at 3:34am | IP Logged |
Warp3 wrote:
The problem with Korean is that it isn't as easily romanized as Japanese due to the more complex phonetic system in Korean, which is partly why so many highly varied romanization systems exist for Korean (and the ones that romanize the most accurately would also be the worst candidates for a romanized input system since the letters used change on the fly to match the sound shifts in Korean).
|
|
|
I have noticed the many romanization systems for Korean. Even among native speakers, sometimes they just randomly choose letters when romanizing it.
The most consistent I've seen was the one in the FSI book, but that one was annoying to read although it was consistent and left no question as to how to pronounce the word in Korean.
That being said, I've taken this into account when mapping out the logic for how a romanized Korean keyboard setup would work :)
Quote:
Honestly, though, in my opinion, it doesn't take that long to learn the Hangul keyboard (I was actually surprised at how soon I was able to turn off the on-screen keyboard, which I had been using for visual reference to remember where each key was initially) and the typing speed is quite good with this layout since the consonants and vowels are mapped to different ends of the keyboard (so you alternate hands much more than typing in English). |
|
|
Yeah, the QWERTY system was actually designed to slow down typists, because back in the day, on typewriters, if you typed too fast, the levers would get stuck together. So QWERTY was developed to slow them down to prevent that malfunction. You probably already knew that, however.
So then there's the Dvorak keyboard layout which was designed to help people type faster. I've heard claims of 20-50% faster on Dvorak than QWERTY.
Quote:
In addition, a big part of the reason that the romanization input systems exist for Chinese and Japanese is because they use ideographs (Hanzi/Kanji) heavily (or in the case of Chinese, exclusively) and there isn't really a good way to "type" an ideograph. Korean has an alphabet, though, which only has a few more characters total than the English alphabet and the extras are easily mapped to SHIFTed letters since Korean doesn't use capitalization. The SHIFTed consonants are easy to remember as they are all the "tensed" versions of the normal consonants (i.e. SHIFT + ㅅ = ㅆ) and there are only two SHIFTed vowels which are both y + vowel versions of the non-SHIFTed character on that key.
I'm not saying that a romanized input system for Korean wouldn't be popular (I'm sure it would be), just that I personally don't see the need for it with Korean given it's differences with the other languages that have that feature. |
|
|
Could be. I just figure I'd rather go to the trouble of programming it than actually learning the Korean keyboard layout. Part ingenuity, part laziness.
I do have an on screen keyboard that I use for reference, too :)
1 person has voted this message useful
| Warp3 Senior Member United States forum_posts.asp?TID= Joined 5536 days ago 1419 posts - 1766 votes Speaks: English* Studies: Spanish, Korean, Japanese
| Message 4 of 21 07 February 2010 at 5:12am | IP Logged |
IronFist wrote:
The most consistent I've seen was the one in the FSI book, but that one was annoying to read although it was consistent and left no question as to how to pronounce the word in Korean.
|
|
|
That's the most consistent I've seen as well with the new "official" Revised Romanization standard not far behind. However, some of the older systems like McCune-Reischauer that weren't consistent tend to be much more accurate for at least approximating the actual sounds made (though many of those systems used diacritical marks which causes other issues).
IronFist wrote:
Yeah, the QWERTY system was actually designed to slow down typists, because back in the day, on typewriters, if you typed too fast, the levers would get stuck together. So QWERTY was developed to slow them down to prevent that malfunction. You probably already knew that, however.
So then there's the Dvorak keyboard layout which was designed to help people type faster. I've heard claims of 20-50% faster on Dvorak than QWERTY.
|
|
|
Actually the QWERTY thing is at least partly a myth and further research shows that the Dvorak keyboard may not be as fast as originally thought: http://www.straightdope.com/columns/read/221/was-the-qwerty- keyboard-purposely-designed-to-slow-typists (Be sure to read the second part which alters/clarifies the original reply notably.)
For what is it worth, I am a touch-typist (I took Typing class back in high school and have never regretted that decision in the least), so it was *really* annoying having to type so slowly in 한글 initially. However, just like with typing in general, the more you practice, the faster you get. I'm still nowhere near my English typing speeds when typing in 한글, but I'm *much* faster than I was when I first started with it a few months ago.
Edited by Warp3 on 07 February 2010 at 5:15am
1 person has voted this message useful
| jimbo Tetraglot Senior Member Canada Joined 6295 days ago 469 posts - 642 votes Speaks: English*, Mandarin, Korean, French Studies: Japanese, Latin
| Message 5 of 21 07 February 2010 at 6:11am | IP Logged |
The Korean keyboard is pretty easy to get to learn how to use.
I put it off for years because I thought it would be a pain to have to memorize another keyboard. It turns out I have
more trouble with the French keyboard layout that the Korean. Maybe it is because the letters are totally different.
1 person has voted this message useful
| Sprachprofi Nonaglot Senior Member Germany learnlangs.comRegistered users can see my Skype Name Joined 6471 days ago 2608 posts - 4866 votes Speaks: German*, English, French, Esperanto, Greek, Mandarin, Latin, Dutch, Italian Studies: Spanish, Arabic (Written), Swahili, Indonesian, Japanese, Modern Hebrew, Portuguese
| Message 6 of 21 07 February 2010 at 9:31am | IP Logged |
I also prefer to use an adapted layout for the foreign languages I type (Greek and Arabic). I could probably learn the different positions of letters, but the punctuation is a bitch; I still haven't memorized the American keyboard layout's punctuation even though my boyfriend's computer uses it AND my computer switches to it when I use DOS or DosBox. Also, the thing is that I don't type much in Greek, even less in Arabic, so I'm afraid of forgetting the layout again.
To easily create your own keyboard layout, use Microsoft Keyboard Layout Creator for Windows or Ukulele for Mac. Ukulele comes with the operating system; Microsoft Keyboard Layout Creator has to be downloaded - just search for msklc.exe online. If you prefer, I can create the layout for you for a small fee.
I really like this tool, as the resulting keyboard layouts are no different from the system ones, so you can activate them in the same way as you would activate the native Korean keyboard, and all programs will support their input, no matter if the programs are Unicode-based or not. Also, this means that you won't need to buy Tavultesoft Keyman, a commercial solution I was using before and whose results are in some ways inferior.
Apart from having handy layouts for Greek and Arabic, I have also created several versions of an international keyboard this way, to help me type French c cedillas, Spanish ñ, Esperanto ĉapelliteroj, Maori macrons, Chinese Pinyin tone marks and several other accented letters that the standard German keyboard doesn't support for no good reason. If I eventually switch to Dvorak, that will be my first priority as well.
1 person has voted this message useful
| Captain Haddock Diglot Senior Member Japan kanjicabinet.tumblr. Joined 6769 days ago 2282 posts - 2814 votes Speaks: English*, Japanese Studies: French, Korean, Ancient Greek
| Message 7 of 21 07 February 2010 at 10:39am | IP Logged |
It's slightly off-topic for this thread, but I'd note that:
• Kana input on a cell phone or iPod is much, much easier and quicker than romaji input.
• Learning kana input on a keyboard, though it takes time at first, is supposedly a lot faster than romaji.
In other words, I think trying the native input method is usually a good idea, and I think there may be a lot of room
for software companies (Apple, Google, and Microsoft) to create new methods for non-Roman scripts.
1 person has voted this message useful
| furyou_gaijin Senior Member Japan Joined 6387 days ago 540 posts - 631 votes Speaks: Latin*
| Message 8 of 21 07 February 2010 at 2:21pm | IP Logged |
Captain Haddock wrote:
It's slightly off-topic for this thread, but I'd note that:
• Kana input on a cell phone or iPod is much, much easier and quicker than romaji input.
|
|
|
Mmm... is it really? Don't you have to press one button five times to get to こ instead of two buttons once? I don't
think it makes much sense for someone who has never used a Japanese cellphone to learn kana input from scratch
on an iPhone.
1 person has voted this message useful
|
This discussion contains 21 messages over 3 pages: 1 2 3 Next >>
You cannot post new topics in this forum - You cannot reply to topics in this forum - You cannot delete your posts in this forum You cannot edit your posts in this forum - You cannot create polls in this forum - You cannot vote in polls in this forum
This page was generated in 0.3359 seconds.
DHTML Menu By Milonic JavaScript
|