Mercurial > vim
view runtime/keymap/korean.vim @ 24982:4cb423b9250d v8.2.3028
patch 8.2.3028: GUI mouse events not tested
Commit: https://github.com/vim/vim/commit/f1e7449d567c630601aa0cec6c663b791785a668
Author: Yegappan Lakshmanan <yegappan@yahoo.com>
Date: Mon Jun 21 18:44:26 2021 +0200
patch 8.2.3028: GUI mouse events not tested
Problem: GUI mouse events not tested.
Solution: Add test_gui_mouse_event(). Add mouse tests. Also add a few
viminfo tests. (Yegappan Lakshmanan, closes #8407)
| author | Bram Moolenaar <Bram@vim.org> |
|---|---|
| date | Mon, 21 Jun 2021 18:45:04 +0200 |
| parents | 29c5f168c6fd |
| children | 11b656e74444 |
line wrap: on
line source
" Maintainer: Jang Whemoon <palindrom615@gmail.com> " Last Change: Nov 24, 2020 " " " " Unlike Japanese or Chinese, modern Korean texts do not depends on conversion " to Hanja (Chinese character). Thus, general Korean text totally can be " covered without help of IME but this keymap. " " BUT, simply mapping each letter of Hangul with sequence of alphabet 1 by 1 " can fail to combine Hangul jamo (conconants and vowels) right. " For example, sequentially pressing `ㅅㅓㅇㅜㄹㄷㅐㅎㅏㄱㅛ` can not only be " combined as `서울대학교`, but alse `성ㅜㄹ댛ㅏㄱ교`, which is totally " nonsense. " Though combining Hangul is deterministic with law that each letter must be " one of (consonant + vowel) or (consonant + vowel + consonant), there is no " way to apply such law without implementing input engine. " " Thus, user of this keymap should wait until previous hangul letter is " completed before typing next one. To reduce such inconvenience, I suggest to " set `timeoutlen` with their own value. (default value is 1000ms) source <sfile>:p:h/korean-dubeolsik_utf-8.vim