[pacman-dev] CVS update of pacman-lib (translation-help)

dan at archlinux.org dan at archlinux.org
Mon Feb 12 11:19:35 EST 2007


    Date: Monday, February 12, 2007 @ 11:19:35
  Author: dan
    Path: /home/cvs-pacman/pacman-lib

Modified: translation-help (1.1 -> 1.2)

* Updated translation-help guide with instructions for updating one po file.


------------------+
 translation-help |   15 ++++++++++-----
 1 file changed, 10 insertions(+), 5 deletions(-)


Index: pacman-lib/translation-help
diff -u pacman-lib/translation-help:1.1 pacman-lib/translation-help:1.2
--- pacman-lib/translation-help:1.1	Wed Feb  7 01:15:56 2007
+++ pacman-lib/translation-help	Mon Feb 12 11:19:35 2007
@@ -21,14 +21,19 @@
 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




More information about the pacman-dev mailing list