Home • Explore • Blog • CI
☰



neovim
2nd chunk of `runtime/doc/mlang.txt`
bc4545dcf0699c43422f2cce245a9d78f6a7db6d066890590000000100000925
 set.  This affects strftime().
			This sets $LC_TIME.
			With the "collate" argument the language used for the
			collation order is set.  This affects sorting of
			characters. This sets $LC_COLLATE.
			Without an argument all are set, and additionally
			$LANG is set.
			The LC_NUMERIC value will always be set to "C" so
			that floating point numbers use '.' as the decimal
			point.  This will make a difference for items that
			depend on the language (some messages, time and date
			format).
			Not fully supported on all systems.
			If this fails there will be an error message.  If it
			succeeds there is no message.  Example: >
				:language
				Current language: C
				:language de_DE.ISO_8859-1
				:language mes
				Current messages language: de_DE.ISO_8859-1
				:lang mes en
<

Message files (vim.mo) have to be placed in "$VIMRUNTIME/lang/xx/LC_MESSAGES",
where "xx" is the abbreviation of the language (mostly two letters). If you
write your own translations you need to generate the .po file and convert it
to a .mo file.

To overrule the automatic choice of the language, set the $LANG variable to
the language of your choice.  use "en" to disable translations. >

  :let $LANG = 'ja'

(text for Windows by Muraoka Taro)

==============================================================================
2. Menus						*multilang-menus*

See |45.2| for the basics, esp. using 'langmenu'.

Note that if changes have been made to the menus after the translation was
done, some of the menus may be shown in English.  Please try contacting the
maintainer of the translation and ask him to update it.  You can find the
name and e-mail address of the translator in
"$VIMRUNTIME/lang/menu_<lang>.vim".

To set the font to use for the menus, use the |:highlight| command.  Example: >

	:highlight Menu font=k12,r12


ALIAS LOCALE NAMES

Unfortunately, the locale names are different on various systems, even though
they are for the same language and encoding.  If you do not get the menu
translations you expected, check the output of this command: >

	echo v:lang

Now check the "$VIMRUNTIME/lang" directory for menu translation files that use
a similar language.  A difference in a "-" being a "_" already causes a file
not to be found!  Another common difference to watch out for is "iso8859-1"
versus "iso_8859-1".  Fortunately
Title: Vim Multi-Language Features: Message Files, Menus, and Locale Aliases
Summary
This section details the location of message files (vim.mo) for translations and how to override the automatic language choice using the $LANG variable. It then discusses multi-language menus, referencing section 45.2 for basics. It explains how to find the translator's contact information for menu updates and how to set the font for menus using the ":highlight" command. Finally, it addresses the issue of different locale names across systems and suggests checking the v:lang variable and the "$VIMRUNTIME/lang" directory for similar language files to resolve translation issues.