We’ve already heard about importing TMX files in the post How to use a translation memory from another tool, so today we will see the inverse operation. Let’s say you have done a translation, or multiple translations, for a customer, and when you deliver they ask you to send to them the translation memory as well, which nowadays and for exchange purposes means converting Transit NXT language pairs to a TMX file. Unless your customer also uses Transit NXT, there would be no use in sending the language pairs directly to them.
To export a language to TMX format, you need to go to Reference material | TMX interface | Export TMX to launch the Create TMX file dialog.
In the Create TMX file dialog that appears, you must indicate what language pairs you want to convert and the name and location of the TMX file that will be generated. To select the language pairs, you can add source files individually, but –specially if you need to convert several language pairs– the most practical way to go is to select projects or, even better, folders. In the screenshot below the three options (files, projects and folders) are used.
You must remember to select the Source language, if it is not selected automatically, and the target language(s) (under Export languages), otherwise the TMX will only contain the source language. In most cases, you do not need to change the other options, so to keep it simple we won’t look into them now.
All files associated with a project, or all files contained in the folder (including subfolders), would be converted, and no matter how many language pairs you select, only one TMX file will be created for all of them. If you add projects, you will be able to choose whether you include also the reference material associated to them or just the working language pairs.
Now you just need to press the Start button. The TMX file will be generated in the location you specified.
Thanks for reading, and please do not hesitate to send your comments or questions or to ask for specific tooltips. Special thanks to Karen Ellis for reviewing this post.
This blog has been moved to a new location, where you will be able to browse it and consult it just like you do now. Stay tuned!