diff options
| author | Bram Moolenaar <Bram@vim.org> | 2015-09-01 20:31:20 +0200 |
|---|---|---|
| committer | Bram Moolenaar <Bram@vim.org> | 2015-09-01 20:31:20 +0200 |
| commit | ac360bf2ca293735fc7c6654dc2b3066f4c62488 (patch) | |
| tree | 904bdc8a17cf04f957ddf3a4408aeeacc8cb6f5b /runtime | |
| parent | 615942452eb74eee7d8386fd3d76a1534181fa06 (diff) | |
| download | vim-ac360bf2ca293735fc7c6654dc2b3066f4c62488.zip | |
patch 7.4.852
Problem: On MS-Windows console Vim uses ANSI APIs for keyboard input and
console output, it cannot input/output Unicode characters.
Solution: Use Unicode APIs for console I/O. (Ken Takata, Yasuhiro Matsumoto)
Diffstat (limited to 'runtime')
| -rw-r--r-- | runtime/doc/options.txt | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/runtime/doc/options.txt b/runtime/doc/options.txt index b3cd34cb3..48793a94d 100644 --- a/runtime/doc/options.txt +++ b/runtime/doc/options.txt @@ -7396,14 +7396,12 @@ A jump table for the options with a short description can be found at |Q_op|. the GUI it only applies to the keyboard ( 'encoding' is used for the display). Except for the Mac when 'macatsui' is off, then 'termencoding' should be "macroman". - In the Win32 console version the default value is the console codepage - when it differs from the ANSI codepage. *E617* Note: This does not apply to the GTK+ 2 GUI. After the GUI has been successfully initialized, 'termencoding' is forcibly set to "utf-8". Any attempts to set a different value will be rejected, and an error message is shown. - For the Win32 GUI 'termencoding' is not used for typed characters, + For the Win32 GUI and console versions 'termencoding' is not used, because the Win32 system always passes Unicode characters. When empty, the same encoding is used as for the 'encoding' option. This is the normal value. |