Jul 27, 2012

Translating "foreign" bilingual tables in memoQ

--- In memoQ@yahoogroups.com, Liset Nyland wrote:
> A client has sent me a 2-column rtf-file export from DVX.
> It looks similar to the MemoQ export but not quite.
> The target column is full of fuzzy matches, so I need to recover these.
> ... do you know if there's a bilingual format exported from DVX that can
> be loaded and translated directly in MemoQ?
There is one way to deal more-or-less directly with the DVX bilingual RTF tables - or any others being introduced by other providers or bilingual tables that some customers are fond of using to store translation strings or other content. I would love to see a general import routine from Kilgray that allows selection of source and target columns of various file types in a dialog, but until then...
1. Get a copy of the PlusToyZ macros by German/English to Ukrainian/Russian translator Arkady Vysotsky.
2. Copy the source and column targets into a separate RTF or MS Word file.
3. Run the PlusToyZ macro to convert that to a Trados-like bilingual (the old Wordfast/Trados RTF/DOC bilingual)
4. Import the converted file to memoQ using the default filter, which is intelligent enough to recognize that you are dealing with Trados-compatible bilingual DOC/RTF.
5. Translate, edit, feed the TM, etc.
6. Export the processed file.
7. Use the appropriate conversion macro in PlusToyZ to turn the data back into a table.
8. Paste the data back into the original bilingual table from DVX or whatever tool it came from.
This is the preferred method to use when your bilingual table is partially pretranslated, or you have a translated table you want to edit while having a better look at the source text. This would also be a useful method for jobs I've had where customers have string or terminology lists in Excel to translate that are in some cases incomplete.

Once you get to Step 3, you can translate that bilingual format in any tool which works with the old Trados RTF/Word segmentation, such as WordFast Classic.I think that was actually the reason Arkady wrote those macros in the first place.

If you want to protect the DVX codes (or similar structures, including placeholders) or store them in the TM as proper tags, run the Regex tagger or use a cascading filter a described in my other blog post about regular expressions for DVX external table translation in memoQ. Of course, for content other than DVX tags, a different regular expression will be needed.


  1. The procedure described here is nice and universal, however there's a little hitch - often bilingual tables contain a TM-match percentage information - this works at least for memoQ and Studio tables. If you'd like to retain this info, you have to choose a different road:
    1. Create a copy of your file.
    2. Remove additional table columns (if present), leaving only source, target and match rate
    3. Drag match rate column in the middle, to get Source-match rate-Target layout
    4. Convert table into text (if you don't know how, see Word help)
    5. Using search and replace insert "{0>" (formatted with tw4winMark style) at the beginning of each line and "<0} at the end
    6. In the Search&Replace dialog select "Use regular expressions" option
    7. Enter "^9([0-9]{1;3})^9" in the Search field, "<}\1{>" in the Replace field (formatted with tw4winMark style).
    8. Use Search&Replace to mark all source text as hidden (search for "\{0\>*\<\}", replace with \1, attribute hidden text).
    9. Save as .doc or .rtf

  2. Good point, Marek, but I might just take your steps and use them to extend Arkady's macros. Lots to be said for automation, and this sort of thing tends to recur as you know.


Notice to spammers: your locations are being traced and fed to the recreational target list for my new line of chemical weapon drones :-)