mirror of
https://github.com/neovim/neovim.git
synced 2026-02-09 05:18:45 +00:00
4076994db6
Several runtime files with "_utf-8" in their filename are actually encoded
in latin1 or cp1255, not UTF-8. This causes errors when tools attempt to
read these files as UTF-8.
Files converted:
- esperanto_utf-8.vim: latin1 -> UTF-8, updated scriptencoding directive
- greek_utf-8.vim: latin1 -> UTF-8
- hebrewp_utf-8.vim: cp1255 (Windows Hebrew) -> UTF-8
- menu_ca.utf-8.vim: latin1 -> UTF-8
- menu_ca_es.utf-8.vim: latin1 -> UTF-8
- menu_pt_pt.utf-8.vim: latin1 -> UTF-8
The actual functionality remains unchanged - only the encoding was modified.
closes: vim/vim#16390
5c855ce43d
Co-authored-by: ThanhNguyxn <thanhnguyentuan2007@gmail.com>
keymap files for Vim
One of these files is loaded when the 'keymap' option is set.
The name of the file consists of these parts:
{language}[-{layout}][_{encoding}].vim
{language} Name of the language (e.g., "hebrew", "greek")
{layout} Optional: name of the keyboard layout (e.g., "spanish",
"russian3"). When omitted the layout of the standard
US-english keyboard is assumed.
{encoding} Optional: character encoding for which this keymap works.
When omitted the "normal" encoding for the language is
assumed.
Use the value the 'encoding' option: lower case only, use '-'
instead of '_'.
Each file starts with a header, naming the maintainer and the date when it was
last changed. If you find a problem in a keymap file, check if you have the
most recent version. If necessary, report a problem to the maintainer.
The format of the keymap lines below "loadkeymap" is explained in the Vim help
files, see ":help keymap-file-format".