Mercurial > vim
comparison runtime/doc/mlang.txt @ 7659:07f11de5efca
commit https://github.com/vim/vim/commit/85084ef1e999dcf50e8d466106a33bac24a0febb
Author: Bram Moolenaar <Bram@vim.org>
Date: Sun Jan 17 22:26:33 2016 +0100
Update help files.
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Sun, 17 Jan 2016 22:30:06 +0100 |
parents | 359743c1f59a |
children | 9f48eab77d62 |
comparison
equal
deleted
inserted
replaced
7658:fc6d585a9726 | 7659:07f11de5efca |
---|---|
1 *mlang.txt* For Vim version 7.4. Last change: 2012 Jan 15 | 1 *mlang.txt* For Vim version 7.4. Last change: 2016 Jan 16 |
2 | 2 |
3 | 3 |
4 VIM REFERENCE MANUAL by Bram Moolenaar | 4 VIM REFERENCE MANUAL by Bram Moolenaar |
5 | 5 |
6 | 6 |
95 | 95 |
96 If you used the self-installing .exe file, message translations should work | 96 If you used the self-installing .exe file, message translations should work |
97 already. Otherwise get the libintl.dll file if you don't have it yet: | 97 already. Otherwise get the libintl.dll file if you don't have it yet: |
98 | 98 |
99 http://sourceforge.net/projects/gettext | 99 http://sourceforge.net/projects/gettext |
100 Or: | |
101 https://mlocati.github.io/gettext-iconv-windows/ | |
100 | 102 |
101 This also contains tools xgettext, msgformat and others. | 103 This also contains tools xgettext, msgformat and others. |
102 | 104 |
103 libintl.dll should be placed in same directory with (g)vim.exe, or some | 105 libintl.dll should be placed in same directory with (g)vim.exe, or some |
104 place where PATH environment value describe. Message files (vim.mo) | 106 place where PATH environment value describe. Vim also finds libintl-8.dll. |
105 have to be placed in "$VIMRUNTIME/lang/xx/LC_MESSAGES", where "xx" is the | 107 Message files (vim.mo) have to be placed in "$VIMRUNTIME/lang/xx/LC_MESSAGES", |
106 abbreviation of the language (mostly two letters). | 108 where "xx" is the abbreviation of the language (mostly two letters). |
107 | 109 |
108 If you write your own translations you need to generate the .po file and | 110 If you write your own translations you need to generate the .po file and |
109 convert it to a .mo file. You need to get the source distribution and read | 111 convert it to a .mo file. You need to get the source distribution and read |
110 the file "src/po/README.txt". | 112 the file "src/po/README.txt". |
111 | 113 |