intltool-update(8) [suse man page]

INTLTOOL-UPDATE(8)					      System Manager's Manual						INTLTOOL-UPDATE(8)

NAME

       intltool-update - updates PO template file and merge translations with it

SYNOPSIS

       intltool-update [option]...
       intltool-update LANGCODE

DESCRIPTION

       intltool-update generates new po file templates from source code, and merges existing translations with these new po templates.

       You must change working directory to the subdirectory containing translations (usually "po/") before running intltool-update.

OPTIONS

       When executing intltool-update , only one mode of operation is allowed each time.

   Mode of operation
       -p
       --pot
	   Generate po template (.pot) only.

       -s
       --headers
	   Executes intltool-extract(8) to extract strings inside XML/INI style files listed in POTFILES.in, and writes the extracted strings into
	   header files, so that the strings can be recognised by xgettext(1).

       -m
       --maintain
	   Search for left out files, which should have been listed in POTFILES.in or POTFILES.skip.  A list of all these files are  written  into
	   another file called "missing".

       -r
       --report
	   Display a status report for all translations in the software.

       -d LANGCODE
       --dist LANGCODE
	   Merge LANGCODE.po with existing PO template.

   Other options
       -g NAME
       --gettext-package=NAME
	   Manually  specify  PO  template file name, instead of determining the name automatically from source. Useful with -p/--pot option. This
	   option has an additional effect: the name of current working directory is no more limited to "po" or "po-*".

       -o FILENAME
       --output-file=FILENAME
	   Manually specify output FILENAME after merging old translation with PO template. Useful either with -d/--dist  option  or  without  any
	   option.

       -x
       --verbose
	   Display lots of feedback.

       --version
	   Show version information.

       --help
	   Show usage and basic help information.

EXAMPLES

       Creates a new PO template from source code, and name it foo.pot:

	 intltool-update --pot --gettext-package=foo

       Updates translation file xy.po using existing po template called "bar.pot", and writes output into "xy1.po":

	 intltool-update --dist --gettext-package=bar --output-file=xy1.po xy

       Creates new PO template and updates translation file xy.po (xy.po is overwritten with new content):

	 intltool-update xy
	 (same as intltool-update --pot && intltool-update --dist xy)

FILES

       po/POTFILES.in
	      Contains list of source files which contain translatable strings, one file per line.

       po/POTFILES.skip
       po/POTFILES.ignore (obsolete)
	      Contains list of source files which should be ignored when searching for translatable strings.

REPORTING BUGS

       Report bugs to http://bugs.launchpad.net/intltool

AUTHOR

       Darin Adler <darin@bentspoon.com>
       Kenneth Christiansen <kenneth@gnu.org>
       Maciej Stachowiak <mjs@eazel.com>

SEE ALSO

       intltoolize(8), intltool-prepare(8), intltool-extract(8), intltool-merge(8), xgettext(1)

intltool							    2003-08-02							INTLTOOL-UPDATE(8)

Check Out this Related Man Page

INTLTOOL-PREPARE(8)					      System Manager's Manual					       INTLTOOL-PREPARE(8)

NAME

       intltool-prepare - Prepare software to make use of intltool

SYNOPSIS

       intltool-prepare [option] [KEYWORD]...

DESCRIPTION

       For  software  packages	that  include  some specific type of translatable files (such as .desktop and .soundlist), before they make use of
       intltool, translators have to dig through them one by one, and add their localization into each file. This process is  error  prone,  since
       translators  may  include  typing  errors, or add their localization in wrong encoding. Besides, translators may not alwas know other files
       (beside .po files) are translatable.

       intltool avoids all the problems above by extracting strings inside those translatable files into po template (.pot) file. All  translators
       need to care about is just translating po files. Afterwards, intltool-merge(8) will merge localized strings into those files.

       Before  your  software  becomes intltool-aware, a few issues have to be sorted out, and intltool-prepare tries to take care of all of them.
       intltool-prepare will:

       o Extract all localized strings in .desktop style files (including ".desktop", ".soundlist", ".keys" and ".directory")  into  corresponding
	 po files.

       o Convert the translatable files into templates that don't contain any localization.

       o Add the list of template files above into POTFILES.in.

       o Add the list of old translatable files into .cvsignore (since they will be generated by intltool later).

       o Add the rules for generating these files into Makefile.am.

       NOTE: You must change working directory to the top level source directory before running intltool-prepare.

OPTIONS

       KEYWORD is a list of additional keywords beside "Name", "Comment" and "description". intltool-prepare will recognize any line starting with
       those KEYWORD and extract localized strings after equal sign ("=").

       -x
       --verbose
	   Be verbose to give user additional feedback.

       -v
       --version
	   Show version information.
       -h
       --help
	   Show usage and basic help information.

REPORTING BUGS

       Report bugs to http://bugs.launchpad.net/intltool

AUTHOR

       Darin Adler <darin@bentspoon.com>
       Kenneth Christiansen <kenneth@gnu.org>
       Maciej Stachowiak <mjs@eazel.com>

SEE ALSO

       intltoolize(8), intltool-update(8), intltool-extract(8), intltool-merge(8)

intltool							    2003-08-02						       INTLTOOL-PREPARE(8)

Linux and UNIX Man Pages

intltool-update(8) [suse man page]

Check Out this Related Man Page