{"id":905,"date":"2018-01-30T22:16:57","date_gmt":"2018-01-30T21:16:57","guid":{"rendered":"http:\/\/wasaty.pl\/blog\/?p=905"},"modified":"2018-11-15T12:09:31","modified_gmt":"2018-11-15T11:09:31","slug":"memsource-files-in-memoq","status":"publish","type":"post","link":"https:\/\/wasaty.pl\/blog\/2018\/01\/30\/memsource-files-in-memoq\/","title":{"rendered":"Memsource files in memoQ"},"content":{"rendered":"
Tweet<\/a><\/div>\n

\"\"When it comes to online CAT-tools I personally consider Memsource as one of the better ones – it’s reasonably fast, offers decent functionality and usability. It’s even better with local (but not offline) client, which can undock some windows, so you can have concordance and TM matches on screen at the same time. Still, it’s not the same as memoQ when it comes to comfort and features, so whenever possible, I process Memsource files in memoQ – that is, if PM allows to download .mxliff files for work with local tool.<\/p>\n

<\/p>\n

To do so I’m running pre-translation with relatively low threshold, download project files and open them in memoQ with another copy in Memsource for concordance and TB checks. After translation I open the files in memsource editor and use upload functionality to synchronize files with the server.
\nUnfortunately, the XLIFF format is a bit loose when it comes to how certain features should be implemented, so things like match rate and translation status are not imported by default and need some tinkering. I have created a template that can be used to import Memsource files in a bit more comfortable way.<\/p>\n

There is a substantial edit concerning the template<\/span>:<\/h3>\n

Originally .mxliff files were modified only before importing into memoQ, and I left cleaning up extra content to memsource editor. Now when you export finished translation, extra bits added for memoQ’s compatibility will be removed<\/span>.<\/strong><\/p>\n

Additionally:<\/p>\n

    \n
  1. Segments confirmed in memoQ will show as confirmed in Memsource. <\/strong>Of course you should still update the Memsource TM.<\/li>\n
  2. Content of “Alt-trans” imported by default to memoQ from Memsource as comment will be ignored now. <\/strong>I was asked by multiple users to disable this. If you want alternative translations from Memsource, you can enable them in memoQ filter filter options.<\/li>\n
  3. I removed my export path rules from template settings – this was causing problems for some users. Still, it’s a good idea to edit export path rules so memoQ will overwrite original files and you won’t have to manually re-name files exported from memoQ (to remove defalut “_iso” target language addition).<\/li>\n<\/ol>\n

    Original post content (still valid):<\/p>\n

    The template work by performing automated actions: the files are edited with regex-based Find and Replace rules to insert additional attributes for match rate and segment states (regex rules are included in .xml configuration files). Subsequently customixed XLIFF filter is used, configured to recognize the introduced attributes and regex-based tagging is run to convert Memsource tags into memoQ tags.<\/p>\n

    To use the template you need to follow instructions below for import and setup. When everything is configured correctly, you can create project from template and work with Memsource files more comfortably. But always remember to back up your files in case something goes wrong<\/strong><\/span>. Also while the conversions and template were tested by two people without any issues (at the time of publication), I can’t predict every possible case and setup, so you are doing this at your own risk – if something goes wrong, I may tray to help, but I won’t be held responsible.<\/p>\n

    Before you start<\/strong>: the template will work only with memoQ 8.x<\/strong> and 7.8<\/strong>, not older. However, executable file “FindAndReplace.exe” is only installed with memoQ version 8.1 and newer. If you have older version, you need to download<\/strong> <\/a>it separately (see below).<\/p>\n

    Template Memsource<\/strong>\u00a0does the following:<\/p>\n