This post is addressed to new users who have started working on their first file in SDL Trados Studio and find that translated segments aren’t getting sent to their Translation Memory (TM).
Assign your TM to the project you’re working on (or add it when you’re opening a document to translate).
If you have been through all the above points and your TM is still not being updated, as a last resort you can import your translated file into the TM.
The Translation Project (the TP, for short) aims to get maintainers and translators of free (open-source) software packages together, so that most computer programs gradually become able to speak many languages.
On these pages you find a list of packages for which translations are handled by the Translation Project, and a list of teams that handle the different languages.
Each team page offers contact information, pointing to mailing lists and home pages.
There is an explanation of why translators need to disclaim the copyright on their translations for the FSF (not assign it, just disclaim it), and an explanation of how to deal with the robot that handles the PO-file submissions.
There are also detailed explanations for package maintainers, for team coordinators, and for individual translators.
If you still have any questions, you can write to the TP coordinators.
The Translation Project only handles translations for packages that have been internationalized through the use of or your local machine for all the details about this package.
If it's not already installed on your machine, you can find the latest version via GNU's mirror list.
To make translations for packages that have been gettextized, translators can use just a simple editor, but programs like Lokalize or po Edit make their work quite a bit easier. If you encountered a translation bug in one of packages handled on this site, please report it to the email address that is given on the relevant team/language page. If you are interested in discussions about translating and translation-related software, consider joining the technical discussion list at