intltool 0.40.6

Feb 13, 2010
Source: ace
+1 +5
Current rating:
intltool 0.40.6 screenshot
intltool collection can be used to do these things:· Extract translatable strings from various source files (, .glade,,,· Collect the extracted strings together with messages from traditional source files (.c, .h) in po/$(PACKAGE).pot.· Merge back the translations from .po files into .xml, .desktop and .oaf files. This merge step will happen at build resp. installation time.The intltool package has a script, intltoolize, which copies the various scripts and does the other magic to your module. So users building from tarballs don't need intltool, only folks building from cvs. (This is modelled on gettextize.)How to Use with autoconf/automake(There is a section for non-auto* configurations below)To use intltool in your module, do the following:· Install intltool, and make sure that the macro it installs is in aclocal's path, or do: export ACLOCAL_FLAGS='-I /usr/local/share/aclocal' · Add these lines to, after the call to gettextize: echo "Running intltoolize" intltoolize --copy --force --automake· Add this line to configure.
in near the top AC_PROG_INTLTOOL([minimum required version], [no-xml]) · Add,, and to EXTRA_DIST in your top-level and also to the top-level .cvsignore. Also add the versions to .cvsignore. · Add intltool-extract, intltool-merge, and intltool-update to DISTCLEANFILES in your top-level· Remove po/ and po/update.* scripts. intltool-update will take over their functionality.At this point, translatable strings will be automatically extracted to the .po files, if you make use of the following recommendations.The intltool-prepare script will help you to prepare the package. It will try to extract translations from existing .desktop files which will become obsolete after intltoolization has taken place.Examples of packages that use intltool are listed in the USED file.
Add Comment
Today's Top Linux Application


OpenSC provides a set of libraries and utilities to work with smart cards. Its main focus is on cards that support cryptographic operations, and facilitates their use in security applications such as authentication, mail encryption, and digital signatures. OpenSC implements the PKCS#11 API so that applications supporting this API (such as Mozilla Firefox and Thunderbird) can use it. On the card, OpenSC implements the PKCS#15 standard, and aims...