Direct import of Trados Studio translation memories has been added. Previously, you would need to export an SDLTM file into an exchange TMX format first (translation memory exchange) and then import it into memoQ. Starting from version 9.4, memoQ allows importing SDLTM files instantly, without any intermediate conversions.
Integration with Protemos has been implemented. From now on, a single click is enough to create a memoQ project out of a Protemos project or, vice versa, immediately create a symmetric Protemos project for an existing memoQ project.
Numerous changes and improvements concerning the use of machine translation plugins.
Smartcat decided to create an open access translation memory based on the materials about the coronavirus
The same goes for Smartcat. It has become complicated these days to write a post without mentioning the name of this ill-fated virus.
Taking into account the numerous texts about the coronavirus, epidemics, etc. being hastily translated in all language directions, Smartcat decided to do a good deed collecting them in a translation memory open to general use—CovidTM, and invites all translation companies to participate in its filling. Once the appropriate materials appear, it will be uploaded as an open access multilingual TMX file. Smartcat promises to fill it with new translations regularly.
Usually, this error doesn’t prevent you from translating. Nevertheless, you can get rid of it.
First, let’s figure out what causes this error.
When you create a package for translation in Trados Studio, each file you add to it gets converted into the SDLXLIFF format, and the translation is performed in this new file.
The name of the SDLXLIFF file is generated in the simplest way possible: by adding the SDLXLIFF extension to the name of the original file. Thus, a file with the name, for instance, Text_to_translate_asap.docx is transformed into the file Text_to_translate_asap.docx.sdlxliff.
By the way, it means that with the file’s name you can reconstruct the name and type of the source file used for its creation very easily. Apparently, a Trados Studio file with the name Translate_right_now!.xlsx.sdlxliff is created from the Excel fileTranslate_right_now!.xlsx.
Once the translation is completed, you face a reverse task: you need to recreate the original file replacing the source text there with the translated one. This operation is called “Clean” and stands for cleaning the source text off the file. To perform this operation, Trados Studio has to store the source file somewhere.
If the source file is small, it is stored right inside the SDLXLIFF file. If it is big, Trados Studio remembers its location to return to it when needed later.
What file’s size is considered small and what is recognized as big is determined by the parameter in Trados Studio that is hidden here:
It equals 20 MB by default. Looking ahead, we need to say that it’s worth increasing this value.
If the work on the project is performed at the same computer where it has been created, no problems usually occur as Trados Studio knows where all original files are stored. But if the files have been moved or if the package is being sent to another computer, Trados Studio will have no access to them.
If Trados Studio gives out the “Dependency file not found” message, it means that it needs the original files, but it has “lost” them. That’s why it will wonder, “Would you like to browse for this file?”—i.e., ask for specifying the path to them.
It will be great if you have the original files. Then you say “Yes” to the question and just specify the path to them. The error disappears, Trados Studio calms down and proceeds with operation as usual.
If you don’t have the original files or if you decided not to specify the path to them, answer “No” as there is no other option actually. You’ll be able to keep working on the text, but some operations with files won’t be available (in particular, Save Target As, Preview, Generate Target Translations, etc.). In most cases, you won’t need them anyway.
Generally, this error doesn’t prevent you from continuing translating: you’ll be able to finish the translation, create the return package, and send the translation to the customer. Since the package was created on their computer, such a problem is not going to puzzle them.
But there are situations when Trados Studio refuses to work because of this error. In this case, the most important is to save the translation memory you’ve been using. It keeps all the segments you’ve translated if you had been confirming them while translating. You’ll be able to use them in the fixed Trados Studio package.
Old Trados 2007 text translation memories can be transformed into the generally accessible TMX format even without Trados 2007
Back in the day, Trados 2007 was the leader in the market of CAT-tools. It consisted of a whole set of powerful programs: TagEditor was used for working with texts, Translator’s Workbench—for working with translation memories, MultiTerm—with terminology, there was a separate module in the form of a Word template and several additional programs. As times go by, Trados 2007 is antique though it is still being used here and there.
In 2009, SDL company launched the first version of a “cat” of the new level—Trados Studio 2009 which broke the neck of Trados 2007.
It is remarkable that Trados 2007 still remains a proprietary program. SDL neither releases it nor shifts it to the category of open software—probably, that is because it is perfectly functional and able to compete with the major SDL product—Trados Studio.
However, many translators of classic vintage still keep some translation memories in Trados 2007 text format, and sometimes there arises a need to convert them to TMX (translation memory exchange) format for importing into any other “cat” or CAT-system. But how to do it if you got rid of Trados 2007 long ago?
Start Xbench. Every technical translator is familiar with this tool. What is more, its free version is perfectly enough for the convertation (you can download the installer from here).
Create a new project in Xbench and upload the Trados 2007 text translation memory:
Here fill out all the necessary fields—specify TMX format, languages of the source and target texts, the name and path to the TMX file—and press ОК.
You get a TMX file containing all segments of the old Trados 2007 text translation memory. As long as TMX is a generally accepted international format, this file can be imported into any “cat”.
There are two notes:
To perform this kind of transformation, the old translation memory is to be a text one—i.e. of TXT format. Unfortunately, Xbench appears back-strapped when facing a 5-file memory.
If you need to apply an old translation memory in Trados Studio, all these operations won’t be necessary. An heir of Trados 2007, Trados Studio supports this format directly. To do this, enter Trados Studio project settings: Project Settings > on the left panel Language Pairs > All Language Pairs > then in the right part of the dialog box press the Add key > File-based Translation Memory...:
A window appears in the bottom right corner; choose the type of Legacy Trados Translation Memory (*.tmw):
State the path to the Trados 2007 5-file translation memory TMW file. Then press Quick Upgrade, wait for all segments to transform, agree to delete temporary files and press OK.
As a result, the old Trados 2007 5-file translation memory is transformed into Trados Studio format. Another file with SDLTM extension will appear in the same folder where files of the translation memory have been stored—this is the very old TM in the new format.
You can search in Trados Studio in both source and target without a mouse!
Like any other serious CAT tool, Trados Studio helps you to simplify your work by allowing you to search in the concordance—i.e., in the translation memory attached to a Trados Studio project you work on. A special shortcut for this feature exists: F3 key. (By the way, it is the same in the ancient Trados 2007.) So, you need to select a word or several words you want to find in the TM(s) and press F3. In the Concordance Search Window, you see the results of searching.
But there is an inconvenience: when you select a fragment in your target text and press F3, the search is automatically performed in the target part of the TM, while, in most cases, you need to search in the source part. And you have to switch the search line to the Source manually.
But there is a shortcut for searching in the source too: CTRL+F3! (It was missing in Trados 2007: you could search in the source ONLY there.)
If your translation memory failed to export, it is not lost yet!
Trados 2007, one of the aged CATs, becomes history gradually. But experienced translators who worked in it still store old translation memories in Trados 2007 format in their archives. Occasionally, it makes sense to involve these antiques in some projects.
Sometimes translation memories become corrupted, due to different reasons. It is still possible to open them in Translator's Workbench, and even to perform translation in TagEditor, but they do not allow you to convert them into some “more modern” CAT format, because when you try to export them into TMX, the program crashes.
The procedure described below can help in such a situation.
1. The first thing you should try is preforming the so called reorganization of the corrupted translation memory. During the reorganization, the index files (i. e., .iix, .mdf, .mtf, and .mwf files) of a 5-file translation memory are being re-created anew from the information from the “container” file (.tmw).
To perform reorganization, in Translator's Workbench, select
File > Reorganise:
The translation memory is reorganized. After that, try to export it to TMX:
File > Export > OK > choose the format, file name and folder where it must be stored.
NOTE: The export command is not accessible, if Exclusive check box was not set when you opened the translation memory in Translator's Workbench.
Is this is a case, close the translation memory and open it again with this check box set.
2. If reorganization or export is failed, sometimes the following trick helps.
Create an empty translation memory with the same name, language direction and structure of custom fields.
Close this translation memory in Translator's Workbench.
Rewrite the .tmw file of the empty TM with the .tmw file of the corrupted TM.
Open the TM you created this way in Translator's Workbench. Opening usually runs smoothly. Do not forget to set the Exclusive check box.
Try to export the TM into TMX format.
If export fails, try to reorganize the TM and to export it one more time.
If reorganization does not help, try to add several new segments into the TM via “usual” translating, and then try to repeat the reorganization/export cycle.
If you fail to export the TM after all these steps, most likely even SDL, the Trados developer, will not help you :(