Translate Toolkit is a toolkit to convert between various different translation formats (such as gettext-based .po formats, OpenOffice.org formats, and Mozilla formats). This makes it possible to stay in one format across all your localisation. Tools to help process and validate localizations, etc.
These documents are currently maintained in the wiki at http://translate.sourceforge.net/wiki/toolkit/index They are also packaged together with the Translate Toolkit source code for distribution - if you are reading this on your local filesystem that is likely how you have got them. If you want the latest version or want to make changes, consult the above wiki.
This Translate Toolkit documentation is under the GNU General Public License (GPL) (everything which is included with the Translate Toolkit and is in the toolkit/ namespace on the wiki). (see copyright).
This is the area for documenting the stable 0.8 branch of the code, for the unstable HEAD branch use toolkit (without the -0.8).
Old Translate Toolkit docs (These have mostly been migrated to the Wiki)
phase
for the complete translation roundtripConverters change many different formats to PO and back again. (Sometimes only one direction is supported, or conversion is done without PO files.)
These use the toolkit but are no part of the toolkit package
The PO tools allow you to manipulate and work with PO files
The scripts are for working with and manipulating PO files. Unlike the tools
which are written in Python, the scripts are written in bash
. They are not installed on your system by default.
There are various tests around, but unit tests are in the process of being added using py.test which you can download from http://code2.codespeak.net/download/py/
To run the tests you do
py.test
from the translate src directory or
py.test storage/test_dtd.py
to run a specific set of tests. The usual procedure for fixing a bug involves adding a unit test to catch it, then making sure the test passes...
Bugs may be reported at bugs.wordforge.org under the “Translate Toolkit” component. More discussion can be had on the translate-devel mailing list
If you would like to contribute to the development of the toolkit then join us on the translate-devel mailing list. And read the developers guide. Note that most new development happens on the HEAD, not on this stable branch.
For information on our conformance to standards, and which features are implemented, see conformance.