| Summary: | uim-byeoru follows system keyboard layout | ||
|---|---|---|---|
| Product: | UIM | Reporter: | YongJoon Joe <developer> |
| Component: | IM: Other IMs | Assignee: | uim-bugs |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
YongJoon Joe
2013-11-16 04:56:17 UTC
Hello, many thanks for using uim-byeoru and reporting the issue. Indeed, this is a known problem stemming from the fact that Korean input does not proceed by mapping each latin alphabet to (a component of) a Korean syllable, as is the case with romaji Japanese input. For a proper implementation of Korean input which would work in an environment like yours, one would need to tell which physical key has been pressed, independent of to which alphabet the key is mapped. One might obtain such information from the X11 keycode or something similar, if byeoru were an X11 application running outside uim. At the level of a uim-scheme code, however, the key press handler receives a key event only after it has been already translated to an ascii code and therefore there is no way to figure out the physical location of the key. [Other developers: please correct me if I missed something.] Fortunately, uim is flexible enough for a workaround, which might work for you unless you switch between qwerty and dvorak too often. It is straightforward to override the default alphabet-jamo mapping which is based on the Korean (and US) layout. You should see immediately which variable to touch once you have a look at byeoru.scm under the scheme source directory of uim. One can override it in the private configuration file. If you are interested in this solution, I would be happy to tell you how in more detail. Cheers, Jae-hyeon (In reply to Jae-hyeon Park from comment #1) > Hello, > > many thanks for using uim-byeoru and reporting the issue. > > Indeed, this is a known problem stemming from the fact that Korean input > does not proceed by mapping each latin alphabet to (a component of) a Korean > syllable, as is the case with romaji Japanese input. For a proper > implementation of Korean input which would work in an environment like > yours, one would need to tell which physical key has been pressed, > independent of to which alphabet the key is mapped. One might obtain such > information from the X11 keycode or something similar, if byeoru were an X11 > application running outside uim. At the level of a uim-scheme code, > however, the key press handler receives a key event only after it has been > already translated to an ascii code and therefore there is no way to figure > out the physical location of the key. [Other developers: please correct me > if I missed something.] > > Fortunately, uim is flexible enough for a workaround, which might work for > you unless you switch between qwerty and dvorak too often. It is > straightforward to override the default alphabet-jamo mapping which is based > on the Korean (and US) layout. You should see immediately which variable to > touch once you have a look at byeoru.scm under the scheme source directory > of uim. One can override it in the private configuration file. If you are > interested in this solution, I would be happy to tell you how in more detail. > > Cheers, > Jae-hyeon Hello. I emailed you, but I leave a message here, too. I have the same problem like Joe. Can you tell us how to make private configuration files? Thanks in advance! If someone want to know the method, please visit my blog below. http://nemonein.egloos.com/5269527 http://nemonein.egloos.com/5269535 Though thery were written in Korean, I don't think it would matter to anyone who concerned about this issue. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.