index : pacman | |
Archlinux32 fork of pacman | gitolite user |
summaryrefslogtreecommitdiff |
author | Dan McGee <dan@archlinux.org> | 2007-02-12 16:19:35 +0000 |
---|---|---|
committer | Dan McGee <dan@archlinux.org> | 2007-02-12 16:19:35 +0000 |
commit | 69d6e5a9ebcdd05287e72b63811d87fe8ea0784f (patch) | |
tree | 04f33272bc43e656167332a575b949970cdfab3d | |
parent | 8cb0758beb5f24ffc827925bbbc3841ca511dc86 (diff) |
-rw-r--r-- | translation-help | 15 |
diff --git a/translation-help b/translation-help index f0e5fbfa..c26c6887 100644 --- a/translation-help +++ b/translation-help @@ -21,14 +21,19 @@ file is the template file for creating new .po files and updating the messages in them when the code changes. First things first. You will need to run ./autogen.sh and ./configure in the -base directory to generate the correct Makefiles. To update the translation +base directory to generate the correct Makefiles. To update all the translation files, run this command: make update-po -At this point, the .pot file rereads the source code and updates its string -list, and the existing po files are merged if necessary to add new messages -or remove old ones. These po files can then either be hand edited, or modified -with a tool such as gtranslator or kbabel. +At this point, the .pot file is regenerated from the source code with an +updated string list, and the existing po files are merged if necessary to add +new messages or remove old ones. These po files can then either be hand edited, +or modified with a tool such as gtranslator or kbabel. + +These steps make it easier to just update your language and not every po file. +If you are working in the src/pacman tree, replace libalpm.pot with pacman.pot: + make libalpm.pot-update + make <po file>-update Making a new language is not too hard, but be sure to follow all the steps. You will have to do the following steps in both the lib/libalpm/po/ and |