Lines Matching refs:encoding

14 |45.3|	Using another encoding
15 |45.4|	Editing files with a different encoding
138 *45.3*	Using another encoding
144 encoding, providing for over ten thousand possible characters.  This still
147 commonly used languages.  This is the "Super encoding that replaces all
152    Nevertheless, when you only edit files that are in the encoding of your
161 internally, you will be able to edit files in any encoding.
168 	:set encoding=utf-8
171 The 'encoding' option tells Vim the encoding of the characters that you use.
173 script files, etc.  You can regard 'encoding' as the setting for the internals
195 Unicode font.  Typed characters still arrive in the encoding of your original
200 	:let &termencoding = &encoding
201 	:set encoding=utf-8
203 This assigns the old value of 'encoding' to 'termencoding' before setting
204 'encoding' to utf-8.  You will have to try out if this really works for your
220 Now you can run Vim inside this terminal.  Set 'encoding' to "utf-8" as
231 	:let &termencoding = &encoding
232 	:set encoding=utf-8
237    For this to work the conversion between 'termencoding' and 'encoding' must
252 	Since 'encoding' is used for all text inside Vim, changing it makes
255 	recommended to set 'encoding' in your vimrc file, and leave it alone.
258 *45.4*	Editing files with a different encoding
262 encoding internally, thus the 16-bit encoding must be converted, since there
263 is a difference between the character set (Unicode) and the encoding (utf-8 or
266 encoding names in the 'fileencodings' option.  When using Unicode, the default
275 	latin1		The good old 8-bit encoding.  Always works.
282    When writing the file, Vim will compare 'fileencoding' with 'encoding'.  If
285 Thus the text is assumed to be encoded with 'encoding'.
295 See |encoding-values| for suggested values.  Other values may work as well.
301 If the automatic detection doesn't work you must tell Vim what encoding the
306 The "++enc" part specifies the name of the encoding to be used for this file
307 only.  Vim will convert the file from the specified encoding, Russian in this
308 example, to 'encoding'.  'fileencoding' will also be set to the specified
309 encoding, so that the reverse conversion can be done when writing the file.
316 	Conversion may result in lost characters.  Conversion from an encoding
347 'encoding'.  If no matching file was found, you will get an error message.
383 	keymap/{name}_{encoding}.vim ~
387 {name} cannot contain an underscore.  Optionally, add the encoding used after
401 	encoding   type			range ~