Translate Toolkit

The Translate Toolkit is a set of software and documentation designed to help make the lives of localizers both more productive and less frustrating. The Toolkit is part of the Translate project, hosted at <https://github.com/translate>.

The software includes programs to covert localization formats to the common PO, and emerging XLIFF format. There are also programs to check and manage PO and XLIFF files. Online documentation includes guides on using the tools, running a localization project and how to localize various projects from OpenOffice.org to Mozilla.

At its core the software contains a set of classes for handling various localization storage formats: DTD, properties, OpenOffice.org GSI/SDF, CSV, MO, Qt .ts, TMX, TBX, WordFast txt, Gettext .mo, Windows RC, and of course PO and XLIFF. It also provides scripts to convert between these formats.

Also part of the Toolkit are Python programs to create word counts, merge translations and perform various checks on translation files.

Important Links

• Latest release downloads
• Documentation, also use --help with any of the commands.
• The Translate Toolkit is released under the GPL with contributions from many people.
• Reporting issues
• Installation

Joining the Translate Project

If you would like to join the translate project mailing list then visit: <http://lists.sourceforge.net/lists/listinfo/translate-devel>.

The vision of the Translate Project is to be a meta project for localizers built on the premise that your language deserves to be a project on its own right not a poor cousin of the main project.

Most projects are inattentive to the needs and difficulties experienced by localizers. To that end the aim is to work towards creating tools and documentation that allows localizers to focus on what they do best: translating software.

Requirements

Note

Please check requirements/*.txt:

pip install -r requirements/recommended.txt

Will install all recommended requirements, while optional.txt will also install support for all other formats.

Python 2.7 or later is required.

Python 2.6 is no longer supported by the Python Software Foundation, while the Toolkit may work in versions before Python 2.7 this is not supported.

The package lxml is needed for XML file processing. You should install version 3.5.0 or later. <http://lxml.de/> Depending on your platform, the easiest way to install might be through your system's package management. Alternatively you can try

pip install lxml

which should install the newest version from the web.

For Mac OSX, the following pages might be of help: <http://lxml.de/build.html#building-lxml-on-macos-x> <http://lxml.de/installation.html#macos-x>

The package lxml has dependencies on libxml2 and libxslt. Please check the lxml site for the recommended versions of these libraries if you need to install them separately at all. Most packaged versions of lxml will already contain these dependencies.

When the environment variable USECPO is set to 1, the toolkit will attempt to use libgettextpo from the gettext-tools package (it might have a slightly different name on your distribution). This can greatly speed up access to PO files, but has not yet been tested as extensively. Feedback is most welcome.

The package iniparse is necessary for ini2po and po2ini. http://code.google.com/p/iniparse/

The python-Levenshtein package will improve performance for fuzzy matching if it is available. This can improve the performance of pot2po, for example. It is optional and no functionality is lost if it is not installed, only speed. <http://sourceforge.net/projects/translate/files/python-Levenshtein/>

Functions in the lang.data module can supply functions to translate language names using the iso-codes package. It can even translate names in the format Language (Country) such as English (South Africa) This is used by Pootle and Virtaal. If the package is not installed, the language names will simply appear in English. It is therefore recommended you install the iso-codes package for your distribution, but it is optional. Alternatively, it is also available from http://packages.debian.org/unstable/source/iso-codes

The package vobject is needed for ical2po and po2ical.

The aeidon package (or gaupol if aeidon is not available) is needed for sub2po and po2sub. Some Unicode encoded files (including most files from <http://dotsub.com/>) require version 0.14 or later. <http://home.gna.org/gaupol/> Gaupol might need the 'Universal Encoding Detector' <http://pypi.python.org/pypi/chardet>

Trados TXT TM support requires the BeautifulSoup parser <http://www.crummy.com/software/BeautifulSoup/>

Program overview

Use --help to find the syntax and options for all programs.

• Converters:

  oo2po    - convert between OpenOffice.org GSI files and PO
  oo2xliff - convert between OpenOffice.org GSI files and XLIFF
  moz2po   - convert between Mozilla files and PO
  csv2po   - convert PO format to CSV for editing in a spreadsheet program
  php2po   - PHP localisable string arrays converter.
  ts2po    - convert Qt Linguist (.ts) files to PO
  txt2po   - convert simple text files to PO
  html2po  - convert HTML to PO (beta)
  xliff2po - XLIFF (XML Localisation Interchange File Format) converter
  prop2po  - convert Java .properties files to PO
  po2wordfast - Wordfast Translation Memory converter
  po2tmx   - TMX (Translation Memory Exchange) converter
  pot2po   - PO file initialiser
  csv2tbx  - Create TBX (TermBase eXchange) files from Comma Separated
             Value (CSV) files
  ini2po   - convert .ini files to to PO
  ical2po  - Convert iCalendar files (*.ics) to PO
  sub2po   - Convert many subtitle files to PO
  resx2po  - convert .Net Resource (.resx) files to PO
  

• Tools (Quality Assurance):

  pofilter - run any of the 40+ checks on your PO files
  pomerge  - merge corrected translations from pofilter back into
             your existing PO files.
  poconflicts - identify conflicting use of terms
  porestructure - restructures po files according to poconflict directives
  pogrep   - find words in PO files
  

• Tools (Other):

  pocompile - create a Gettext MO files from PO or XLIFF files
  pocount   - count translatable file formats (PO, XLIFF)
  podebug   - Create comment in your PO files' msgstr which can
              then be used to quickly track down mistranslations
              as the comments appear in the application.
  posegment - Break a PO or XLIFF files into sentence segments,
              useful for creating a segmented translation memory.
  poswap    - uses a translation of another language that you
              would rather use than English as source language
  poterminology - analyse PO or POT files to build a list of
                  frequently occurring words and phrases