You can easily remove the source text from Trados Word files, even without Trados.
When your translation performed in Word with Trados (to be exact, Translator's Workbench) is finished, you create a translated file that contains the translation. I. e., you eliminate the source text and leave the translated text (target) only. This operation is called “cleaning”, as you “clean” your file from source, leaving the target only.
Usually, you do it using the Translator's Workbench: you select Tools > Clean Up, then you choose the Word files, press Clean Up. Translator's Workbench deletes the source text and so you get the translated files.
But sometimes something goes wrong and Translator's Workbench fails to clean the files. This usually happens if there are problems with segmentation in the file you are cleaning. Or, you try to clean the files of Word 2007 and higher (.docx files). Or, you need to clean the file from source on a PC where Trados is not installed at all. Then, the following trick helps.
1. Usually, you see only visible text in Word, like this:
You see the translated text only, while the source text is present in the file as well, but it is hidden. To see the source text, you need to make hidden Word text visible: press button on the Word ribbon or press CTRL+SHIFT+8 (just 8, not F8). You will see something like this:
2. To get rid of the source text is in fact to get rid of the hidden text. This can be done right in Word, without Trados. To do this, press CTRL+H to open Search and Replace dialog window, then press More, then press Format button > Font > Hidden:
Then, press OK and Replace All.
This command deletes all hidden text from a Word file, leaving only visible one — i. e., only your translation.
Hidden text function helps to see non-visible defects
Look at the picture:
It is a screen shot from Word document. Yes, it is the first stanza from famous Lewis Carroll's “Jabberwocky.” Of course, there are many non-existing words there, that is why Word underlines them. But everything else seems to be ok.
BUT no: there are many defects in these four lines! The problem is your eyes do not catch them, as they are hidden.
To see them, you need to make the hidden text visible by pressing CTRL+SHIFT+8 (number 8, not F8 key) or clicking the following button on the ribbon:
(It is on the Home tab of the Word ribbon.) Then we see:
As we can see, the defects are many. The 1st line ends with multiple trailing spaces. There are several double spaces in the 2nd one. (This is the only problem on the picture, that could be caught with “unaided eye.”) The 2nd and the 3rd lines have line breaks instead of paragraph signs (and due to this, lines 2-4 are actually a single paragraph with two line breaks). The 4th line contains unnecessary non-breaking spaces instead of regular ones. (The small circlets here are not the degree signs, they are non-breaking spaces. We will discuss them in the upcoming posts.)
Strictly speaking, all these issues are errors, and they require correcting. And, to catch such issues, you need just to make them visible.
There is an easy 2-step way to convert Wordfast translation memory from custom .txt format into the generally acceptable .tmx format
The easiest way to perform such conversion is to use Xbench. The free 2.9.0. Xbench build is enough. Yes, this tool is good not only for QA :) You do not even need Wordfast itself.
1. Load the .txt file containing the offline Wordfast TM to the Xbench, as if it is a regular bilingual file. (If the TM is big, this process can last for some time.) Xbench recognizes it:
2. Export the loaded segments into the .tmx file. To do this, press CTRL+R or select Tools > Export Items:
In the Language section, choose source and target languages of the TM.
The result of this operation is the .tmx file containing the segments from the initial Wordfast .txt translation memory. TMX is the industry standard format for exchanging translation memories data. Actually, TMX = Translation Memory eXchange. Now you can import it in any CAT tool.
There is a simple way to extract .xlf from memoQ .mqxlz
Sometimes you have a memoQ XLIFF file (with .mqxlz extension), but it is much easier for you to work with .xlf file. (For example, .xlf files, unlike .mqxlz ones, allow performing the QA checks in the free version of Xbench.)
The trick described below helps:
1. First, you should know that .mqxlz file is actually the renamed .zip archive. Add the .zip extension to .mqxlz file:
my_memoQ_file.mqxlz -> my_memoQ_file.mqxlz.zip
2. Extract everything from this .zip file. There are two files inside the .zip:
3. Add the .xlf extension to .mqxliff file (you do not need skeleton.xml at all):
document.mqxliff -> document.mqxliff.xlf
So, you get the .xlf file containing the same bilingual text.