Mercurial > vim
view runtime/keymap/korean.vim @ 30992:c207a462320a v9.0.0831
patch 9.0.0831: compiler warning for redefining HAVE_DUP
Commit: https://github.com/vim/vim/commit/6c3d3e69047438ff5b7f58d44fe66af9e2c4212b
Author: ichizok <gclient.gaap@gmail.com>
Date: Fri Nov 4 22:38:11 2022 +0000
patch 9.0.0831: compiler warning for redefining HAVE_DUP
Problem: Compiler warning for redefining HAVE_DUP.
Solution: Undefine HAVE_DUP if needed. (Ozaki Kiichi, closes https://github.com/vim/vim/issues/11484)
| author | Bram Moolenaar <Bram@vim.org> |
|---|---|
| date | Fri, 04 Nov 2022 23:45:04 +0100 |
| parents | 11b656e74444 |
| children |
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 also `성ㅜㄹ댛ㅏㄱ교`, 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