Mercurial > vim

view runtime/keymap/korean.vim @ 24301:c5cb45fc82d3 v8.2.2691

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
patch 8.2.2691: autoconf may mess up compiler flags Commit: https://github.com/vim/vim/commit/3fa5e64e0ed55de718e48d0268edc360b2352bc1 Author: Bram Moolenaar <Bram@vim.org> Date: Fri Apr 2 13:30:59 2021 +0200 patch 8.2.2691: autoconf may mess up compiler flags Problem: Autoconf may mess up compiler flags. Solution: Handle removing FORTIFY_SOURCE a bit better. (Vladimir Lomov, closes #8049)
author Bram Moolenaar <Bram@vim.org>
date Fri, 02 Apr 2021 13:45:03 +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