Multi-directional translation memory
Variations on TM
In a recent post about new pretranslation options, we mentioned the fact that Transit NXT is the only TEnT that can create multi-directional translation memories. In practice, this feature means that, for example, a multilingual project with 3 language combinations - ENG as the source and ESP, DEU and FRA as target languages - gives you reference material for 4 x (4 - 1) = 12 different language combinations:
Short cuts – Nº 15 : New options for converting language pairs to the standard TMX file format
In one of the tooltips, we learnt how to convert language pairs into the standard TMX format. The new Service Pack includes the following additional useful features for this conversion process. These new features give you added productivity, more efficiency and added quality control:
Special edition: Transit NXT Service Pack 7 is here !
The long awaited Transit NXT Service Pack 7 is released ! It comes packed with a host of new features, modules, filters and improvements.To treat all the novelties in one blog post would be impossible. So, in this post, we offer you a summary of all the new stuff that you will encounter in what might righteously be called the "new version" of Transit NXT.
Short cuts – Nº 11 : Converting and using TMX files as reference material
If you often receive translation memories in TMX format and are wondering about how to use them in Transit, here is a quick way to convert them into language pairs to be used in Transit NXT as reference material.
Select TMX interface | Import TMX from the Reference material button in the resource bar as shown in the figure below:
Using public corpora in Transit NXT
Welcome to a new tooltip about Transit NXT. Today we would like to mention a very useful resource. The translation workload of some big international institutions generates a lot of reference material, which can be used by anyone if they release it in a suitable form, for example the translation memory exchange format (TMX).
Creating a TMX file for your client
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.
How to use a translation memory from another tool
Welcome to a new tooltip about Transit NXT. In this tooltip we will see how to integrate data coming from a source other than Transit NXT into your translation memory and the role that exchange standards play in that. Let's see a simple case. Imagine a client has asked you to translate the new version (v. 2.0) of a document that was already translated by someone else into your target language.