Mercurial > vim

comparison runtime/keymap/korean.vim @ 23047:29c5f168c6fd

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Update runtime files Commit: https://github.com/vim/vim/commit/23515b4ef7580af8b9d3b964a558ab2007cacda5 Author: Bram Moolenaar <Bram@vim.org> Date: Sun Nov 29 14:36:24 2020 +0100 Update runtime files
author Bram Moolenaar <Bram@vim.org>
date Sun, 29 Nov 2020 14:45:04 +0100
parents
children 11b656e74444
comparison
equal deleted inserted replaced
23046:9a30b28b8154 23047:29c5f168c6fd
1 " Maintainer: Jang Whemoon <palindrom615@gmail.com>
2 " Last Change: Nov 24, 2020
3 "
4 "
5 "
6 " Unlike Japanese or Chinese, modern Korean texts do not depends on conversion
7 " to Hanja (Chinese character). Thus, general Korean text totally can be
8 " covered without help of IME but this keymap.
9 "
10 " BUT, simply mapping each letter of Hangul with sequence of alphabet 1 by 1
11 " can fail to combine Hangul jamo (conconants and vowels) right.
12 " For example, sequentially pressing `ㅅㅓㅇㅜㄹㄷㅐㅎㅏㄱㅛ` can not only be
13 " combined as `서울대학교`, but alse `성ㅜㄹ댛ㅏㄱ교`, which is totally
14 " nonsense.
15 " Though combining Hangul is deterministic with law that each letter must be
16 " one of (consonant + vowel) or (consonant + vowel + consonant), there is no
17 " way to apply such law without implementing input engine.
18 "
19 " Thus, user of this keymap should wait until previous hangul letter is
20 " completed before typing next one. To reduce such inconvenience, I suggest to
21 " set `timeoutlen` with their own value. (default value is 1000ms)
22
23 source <sfile>:p:h/korean-dubeolsik_utf-8.vim