The gettext lint tools is a collection of tools for checking the validity, consistency and spelling of PO and POT files. The project also includes an experimental glossary building tool.
Here are some key features of "gettext lint tools":
· POFileStatus - validator and status reporting
· POFileChecker - searches for common mistakes in PO/POT files
· POFileConsistency - consistency checker
· POFileEquiv - glossary generator
· POFileSpell - spell checker
· POFileFill - fill a file with entries already translated in other files
All the commands produce XML output; you can feed this output to report.xsl (probably located on /usr/share/gettext-lint/report.xsl) to generate HTML reports. For example:
POFileChecker $(find /path/to/po/files -name "*.po") | xsltproc /usr/share/gettext-lint/report.xsl - > report.html
The included XSL can receive the parameter 'css' with the name of a stylesheet
to reference in the resulting HTML. For example:
POFileChecker $(find /path/to/po/files -name "*.po") | xsltproc -param css "'/usr/share/gettext-lint/report.css'" /usr/share/gettext-lint/report.xsl - > report.html
You can also run POFileSpell and POFileConsistency in interactive mode,
following a series of prompts. The -i option chooses this mode.
Installation
The `configure' shell script attempts to guess correct values for various ystem-dependent variables used during compilation. It uses those values to create a `Makefile' in each directory of the package. It may also create one or more `.h' files containing system-dependent definitions. Finally, it creates a shell script `config.status' that you can run in the future to recreate the current configuration, and a file `config.log' containing compiler output (useful mainly for debugging `configure').
It can also use an optional file (typically called `config.cache' and enabled with `--cache-file=config.cache' or simply `-C') that saves the results of its tests to speed up reconfiguring. (Caching is disabled by default to prevent problems with accidental use of stale cache files.)
If you need to do unusual things to compile the package, please try to figure out how `configure' could check whether to do them, and mail diffs or instructions to the address given in the `README' so they can be considered for the next release. If you are using the cache, and at some point `config.cache' contains results you don't want to keep, you
may remove or edit it.
The file `configure.ac' (or `configure.in') is used to create `configure' by a program called `autoconf'. You only need `configure.ac' if you want to change it or regenerate `configure' using a newer version of `autoconf'.
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type `./configure' to configure the package for your system. If you're using `csh' on an old version of System V, you might need to type `sh ./configure' instead to prevent `csh' from trying to execute
`configure' itself.
Running `configure' takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Optionally, type `make check' to run any self-tests that come with the package.
4. Type `make install' to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean'. To also remove the files that `configure' created (so you can compile the package for a different kind of computer), type `make distclean'. There is
also a `make maintainer-clean' target, but that is intended mainly for the package's developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
What's New in This Release:
· add POFileGlossary, a tool to check a translation against an existing glossary.
· add POFileClean, a tool to eliminate translations that are not translated.
· corrected several bugs in several tools, mainly POFileEquiv.
Product's homepage
Find us on Google+
