Translate Toolkit

The Translate Toolkit is a toolkit to convert between various different translation formats (such as gettext-based .po formats, Mozilla formats and OpenOffice.org formats).

This makes it possible to stay in one format across all your localisation, thus allowing you to master one translation editor instead of one per project. Of course an added benefit is that now you cannot create broken OpenOffice.org or Mozilla translation files. And of course their are many other [benefits].

The toolkit also includes tools to help check, validate, merge and extract from your localizations.

Here are some key features of "Translate Toolkit":

￭ Work with ONE localisation format. You'll no longer be editing DTD files in one tools, .properties in another, OpenOffice GSI in a third. Simply do all your localisation in a PO editor ￭ Converters for a number of formats: OpenOffice.org SDF/GSI, .properties, DTD, XHTML, .inc, .ini, Comma Seperated Value, TMX, XLIFF, TBX ￭ Output VALID target file types. We make sure that your output files (eg .properties) contain all comments from the original file and preserves the layout of the original as far as possible. If your PO entry is marked as fuzzy we use the English text, not your half complete translation. The convetors for OpenOffice.org and Mozilla formats will also perform simple checks and corrections to make sure you have none of those hard to find localisation bugs. ￭ Our checker has over 39 checks to find errors such as: missing or translated variables, missing accelerator keys, bad escaping, start capitalisation, missing setences, bad XML and much more. ￭ Find conflicting translations easily, cases where you have translated a source word differently or used a target word for 2 very different English concepts ￭ Extract messages using simple text or a regular expresion allowing you to quickly find and extract words that you need to fix due to glossary changes. ￭ Merge snippets of PO files into your existing translations. ￭ Create word, string and file counts of your PO files. Making it much easier to budget time as string counts do not give you a good indication of expected work. ￭ Create a set of PO files with debuging entries to allow you to easily locate the source of translations. Very useful in OpenOffice.org which provides scant clues as to where the running application has sourced the message.

Requirements:

￭ Python