Mercurial > vim
annotate src/po/README.txt @ 9031:8208f5f58505 v7.4.1801
commit https://github.com/vim/vim/commit/113ce084569893a3897c8cc4d7d0f301fef7978a
Author: Bram Moolenaar <Bram@vim.org>
Date: Sat Apr 30 12:32:52 2016 +0200
patch 7.4.1801
Problem: Make uninstall leaves file behind.
Solution: Delete rgb.txt. (Kazunobu Kuriyama)
| author | Christian Brabandt <cb@256bit.org> |
|---|---|
| date | Sat, 30 Apr 2016 12:45:05 +0200 |
| parents | ceb5f21cda79 |
| children | 49c12c93abf3 |
| rev | line source |
|---|---|
| 7 | 1 TRANSLATING VIM MESSAGES |
| 2 | |
| 3 In this directory you will find xx.po files, where "xx" is a language code. | |
| 4 Each file contains the translation of English Vim messages for one language. | |
| 5 The files are in "po" format, used by the gettext package. Please refer to | |
| 6 the gettext documentation for more information. | |
| 7 | |
| 8 The GNU gettext library, starting with version 0.10.37, supports converting | |
| 9 messages from one encoding to another. This requires that it was compiled | |
| 10 with HAVE_ICONV. The result is that the messages may be in any encoding | |
| 11 supported by iconv and will be automatically converted to the currently used | |
| 12 encoding. | |
| 13 | |
| 14 The GNU gettext library, starting with version 0.10.36, uses a new format for | |
| 1125 | 15 some encodings. This follows the C99 standard for strings. It means that |
| 16 when a multi-byte character includes the 0x5c byte, this is not recognized as | |
| 17 a backslash. Since this format is incompatible with Solaris, Vim uses the old | |
| 7 | 18 format. This is done by setting the OLD_PO_FILE_OUTPUT and OLD_PO_FILE_INPUT |
| 19 environment variables. When you use the Makefile in this directory that will | |
| 20 be done for you. This does NOT work with gettext 0.10.36. Don't use it, get | |
| 21 0.10.37. | |
| 22 | |
| 23 | |
| 24 ON MS-WINDOWS | |
| 25 | |
| 26 The distributed files are generated on Unix, but this should also be possible | |
| 27 on MS-Windows. Download the gettext packages, for example from: | |
| 28 | |
| 29 http://sourceforge.net/projects/gettext | |
| 30 | |
| 31 You might have to do the commands manually. Example: | |
| 32 | |
| 1125 | 33 cd c:\vim\vim71 |
| 7 | 34 mkdir runtime\lang\ja\LC_MESSAGES |
| 35 msgfmt -o runtime\lang\ja\LC_MESSAGES\vim.mo src\po\ja.po | |
| 36 | |
| 37 | |
| 38 WHEN THERE IS A MISTAKE | |
| 39 | |
| 40 If you find there is a mistake in one of the translations, please report this | |
| 41 to the maintainer of the translation. His/her E-mail address is in the | |
| 42 comments at the start of the file. You can also see this with the ":messages" | |
| 43 command in Vim when the translation is being used. | |
| 44 | |
| 45 | |
| 46 CREATING A NEW PO FILE | |
| 47 | |
| 48 We will use "xx.po" as an example here, replace "xx" with the name of your | |
| 49 language. | |
| 50 | |
| 51 - Edit Makefile to add xx to LANGUAGES and xx.mo to MOFILES. | |
| 52 - Copy the header of an existing file, e.g., de.po, to xx.po. Do not copy any | |
| 53 of the translated messages, delete everything after the "msgstr". | |
| 54 - The remaining work is like updating, see the next section. | |
| 55 | |
| 56 | |
| 57 UPDATING A PO FILE | |
| 58 | |
| 59 If you are the maintainer of a .po file, this is how you update the file. We | |
| 60 will use "xx.po" as an example here, replace "xx" with the name of your | |
| 61 language. | |
| 62 | |
| 63 (1) Add new and changed messages from the Vim sources: | |
| 64 | |
| 65 make xx | |
| 66 | |
| 67 This will extract all the strings from Vim and merge them in with the | |
| 4992 | 68 existing translations. Requires the GNU gettext utilities. |
| 7 | 69 Your original xx.po file will be copied to xx.po.orig |
| 70 | |
| 71 -- After you do this, you MUST do the next three steps! -- | |
| 72 | |
| 73 (2) Translate | |
| 74 See the gettext documentation on how to do this. You can also find | |
| 75 examples in the other po files. | |
| 76 Search the po file for items that require translation: | |
| 77 | |
| 78 /fuzzy\|^msgstr ""\(\n"\)\@! | |
| 79 | |
| 80 Remove the "#, fuzzy" line after adding the translation. | |
| 81 | |
| 82 There is one special message: | |
| 83 msgid "Messages maintainer: Bram Moolenaar <Bram@vim.org>" | |
| 84 You should include your name and E-mail address instead, for example: | |
| 85 msgstr "Berichten übersetzt bei: John Doe <john@doe.org>" | |
| 86 | |
| 87 (3) Clean up | |
| 88 This is very important to make sure the translation works on all systems. | |
| 89 Comment-out all non-translated strings. There are two types: | |
| 90 - items marked with "#, fuzzy" | |
| 91 - items with an empty msgstr | |
| 92 You can do this with the cleanup.vim script: | |
| 93 | |
| 94 :source cleanup.vim | |
| 95 | |
| 96 Background: on Solaris an empty msgstr results in an empty message; GNU | |
| 97 gettext ignores empty strings and items marked with "#, fuzzy". | |
| 98 | |
| 449 | 99 This also removes the line numbers from the file, so that patches are not |
| 100 messed up by changes in line numbers and show the actual changes in the | |
| 101 text. | |
| 102 | |
| 7 | 103 (4) Check: |
| 104 | |
| 440 | 105 vim -S check.vim xx.po |
| 7 | 106 make xx.mo |
| 107 | |
| 108 Look out for syntax errors and fix them. | |
|
4502
605c9ce57ec3
Updated runtime files, language files and translations.
Bram Moolenaar <bram@vim.org>
parents:
1125
diff
changeset
|
109 |
|
605c9ce57ec3
Updated runtime files, language files and translations.
Bram Moolenaar <bram@vim.org>
parents:
1125
diff
changeset
|
110 |
|
605c9ce57ec3
Updated runtime files, language files and translations.
Bram Moolenaar <bram@vim.org>
parents:
1125
diff
changeset
|
111 USING GETTEXT WITHOUT ICONV |
|
605c9ce57ec3
Updated runtime files, language files and translations.
Bram Moolenaar <bram@vim.org>
parents:
1125
diff
changeset
|
112 |
|
605c9ce57ec3
Updated runtime files, language files and translations.
Bram Moolenaar <bram@vim.org>
parents:
1125
diff
changeset
|
113 When using gettext which doesn't support iconv, the encoding of the .mo file |
|
605c9ce57ec3
Updated runtime files, language files and translations.
Bram Moolenaar <bram@vim.org>
parents:
1125
diff
changeset
|
114 must match your active encoding. For that you must convert and change |
|
605c9ce57ec3
Updated runtime files, language files and translations.
Bram Moolenaar <bram@vim.org>
parents:
1125
diff
changeset
|
115 encoding of *.po file in advance of generating the *.mo file. For example, to |
|
605c9ce57ec3
Updated runtime files, language files and translations.
Bram Moolenaar <bram@vim.org>
parents:
1125
diff
changeset
|
116 convert ja.po to EUC-JP (supposed as your system encoding): |
|
605c9ce57ec3
Updated runtime files, language files and translations.
Bram Moolenaar <bram@vim.org>
parents:
1125
diff
changeset
|
117 |
|
605c9ce57ec3
Updated runtime files, language files and translations.
Bram Moolenaar <bram@vim.org>
parents:
1125
diff
changeset
|
118 (1) Convert the file encoding: |
|
605c9ce57ec3
Updated runtime files, language files and translations.
Bram Moolenaar <bram@vim.org>
parents:
1125
diff
changeset
|
119 |
|
605c9ce57ec3
Updated runtime files, language files and translations.
Bram Moolenaar <bram@vim.org>
parents:
1125
diff
changeset
|
120 mv ja.po ja.po.orig |
|
605c9ce57ec3
Updated runtime files, language files and translations.
Bram Moolenaar <bram@vim.org>
parents:
1125
diff
changeset
|
121 iconv -f utf-8 -t euc-jp ja.po.orig > ja.po |
|
605c9ce57ec3
Updated runtime files, language files and translations.
Bram Moolenaar <bram@vim.org>
parents:
1125
diff
changeset
|
122 |
|
605c9ce57ec3
Updated runtime files, language files and translations.
Bram Moolenaar <bram@vim.org>
parents:
1125
diff
changeset
|
123 (2) Rewrite charset declaration in the file: |
|
605c9ce57ec3
Updated runtime files, language files and translations.
Bram Moolenaar <bram@vim.org>
parents:
1125
diff
changeset
|
124 |
|
605c9ce57ec3
Updated runtime files, language files and translations.
Bram Moolenaar <bram@vim.org>
parents:
1125
diff
changeset
|
125 Open ja.po find this line: |
|
605c9ce57ec3
Updated runtime files, language files and translations.
Bram Moolenaar <bram@vim.org>
parents:
1125
diff
changeset
|
126 "Content-Type: text/plain; charset=utf-8\n" |
|
605c9ce57ec3
Updated runtime files, language files and translations.
Bram Moolenaar <bram@vim.org>
parents:
1125
diff
changeset
|
127 You should change "charset" like this: |
|
605c9ce57ec3
Updated runtime files, language files and translations.
Bram Moolenaar <bram@vim.org>
parents:
1125
diff
changeset
|
128 "Content-Type: text/plain; charset=euc-jp\n" |
|
605c9ce57ec3
Updated runtime files, language files and translations.
Bram Moolenaar <bram@vim.org>
parents:
1125
diff
changeset
|
129 |
|
605c9ce57ec3
Updated runtime files, language files and translations.
Bram Moolenaar <bram@vim.org>
parents:
1125
diff
changeset
|
130 There are examples in the Makefile for the conversions already supported. |