@@ -182,11 +185,11 @@ Extracting translatable strings Now, it is time to extract the strings to be translated from the program source code. This is achieved with xgettext, which can be invoked as follows:


-  xgettext -d hello -s -o hello.pot hello.c
+  xgettext -d hello -o hello.pot hello.c

This processes the source code in hello.c, saving the output in hello.pot (the -argument to the -o option). The -s option tells xgettext to produce sorted -output. The message domain for the program should be specified as the argument +argument to the -o option). +The message domain for the program should be specified as the argument to the -d option, and should match the domain specified in the call to textdomain (on line 9 of the program source). Other details on how to use gettext can be found from ``man gettext.'' @@ -457,14 +460,14 @@ Merging old and new translations As before, extract the translatable strings from hello.c to a new portable object template file, hello-new.pot, using xgettext,


-  xgettext -d hello -s -o hello-new.pot hello.c
+  xgettext -d hello -o hello-new.pot hello.c

Now, we use a new program, msgmerge, to merge the existing .po file with translations into the new template file, viz.,


-  msgmerge -s -U oriya.po hello-new.pot
+  msgmerge -U oriya.po hello-new.pot

-The -s option produces sorted output, and the -U option updates the existing +The -U option updates the existing .po file, oriya.po. We could have chosen to instead create a new .po file by using ``-o <filename>'' instead of -U. The updated .po file will still have the old translations embedded in it, and new entries with untranslated @@ -713,7 +716,8 @@ The command line arguments were:

The translation was initiated by Gora Mohanty on 2004-07-24

A tutorial on Native Language Support using GNU gettext