Tony Mechelynck 写道: > I'm not sure. I suppose that option was defined before Unicode became > well-known, maybe even before it existed, when most charsets were of the > 8-bit kind except for East-Asian scripts, which required "special" MBCS > versions of the OSes anyway (such as MS-DOS 2.25). > > Once the Unicode standard was published, it included not only mappings > of codepoints to glyphs but also quite a lot of metadata about these > codepoints (such as wide vs. narrow vs. ambiguous, LTR vs. RTL vs. > ambiguous, lower/ upper/ titlecase, punctuation, number systems, etc.). > However, Vim versions with -multi_byte must still be supported, and they > don't have access to that wealth of meta-information. Also, IIUC it's in > the ASCII range that there is most variation between programming > languages, operating systems, human languages, etc. concerning which > characters may be used in which circumstances.
Human languages of CJK are not in the ASCII range at all and I bet CJK have more than 30% of the world population. Vim is for programmers, is it _only_ for programmers? The difficulties may be that 'iskeyword' is a whitelist, not a blacklist, we cannot easily blacklist a single Unicode character in 'iskeyword' without knowing *all* the Unicode characters which matches iswalpha(). Perhaps the simplest approach is to add an option 'isnkeyword' which supports any Unicode character and we can blacklist some Unicode characters while still retain the 'iskeyword' option functioning. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
