{"id":872,"date":"2015-11-07T16:13:34","date_gmt":"2015-11-07T15:13:34","guid":{"rendered":"http:\/\/wasaty.pl\/blog\/?p=872"},"modified":"2015-11-07T16:13:34","modified_gmt":"2015-11-07T15:13:34","slug":"importing-studio-tm-and-tb-into-memoq","status":"publish","type":"post","link":"https:\/\/wasaty.pl\/blog\/2015\/11\/07\/importing-studio-tm-and-tb-into-memoq\/","title":{"rendered":"Importing Studio TM and TB into memoQ"},"content":{"rendered":"
Tweet<\/a><\/div>\n

\"new_memoQ\"<\/a>memoQ is great tool with many interoperability features, including easy SDLXLIFF file import\/export,\u00a0ability to import Studio packages and generating\u00a0Studio return packages. And while packages are imported with translation memories and term bases, strangely the ability to import stand-alone Studio TMs (SDLTM) and TBs (SDLTB) is nowhere to be found in the UI. And this can be a seroius problem if a client sends you SDLXLIFF and SDLTM files instead of proper package (happens often enough). And while there is a solution to this problem<\/a><\/strong>, I’m offering a relatively simple alternative.<\/p>\n

<\/p>\n

Since memoQ can import both TM and TB native formats as parts of Studio package, all we need is to add the files we need into a proper Studio package and import it into memoQ. Using a simple package as a starting point I’ve created a bogus Studio package you can use to import the files you need. Here’s how:<\/p>\n

    \n
  1. Download this file<\/a><\/strong>.<\/li>\n
  2. Unpack its content to an empty folder (e.g. “Package”)<\/li>\n
  3. Go to TM folder.<\/li>\n
  4. Copy the TM file you need to import (e.g. “My_Studio_TM”) into this folder (optional: you can delete “Example_TM.sdltm” file)<\/li>\n
  5. \u00a0Browse one level up, to folder “Package”.<\/li>\n
  6. Go to Termbases folder.<\/li>\n
  7. Copy the TB file you need to import (e.g. “My_Studio_TB”) into this folder (optional: you can delete “Example_TB.sdltb” file).<\/li>\n
  8. Browse one level up, to folder “Package”.<\/li>\n
  9. Open “Import_wrapper.sdlproj” with text editor (right click the file, select “Open with” and choose Notepad or any other text editor).
    \nOptionally you can rename the file, adding extention .txt, which will help with file editing.<\/li>\n
  10. Find string “Example_TM.sdltm” and replace it with the name of the TM you want to import (e.g. “My_Studio_TM.sdltm”).<\/li>\n
  11. Find string “Example_TB.sdltb” and replace it with the name of the TB you want to import (e.g. “My_Studio_TB.sdltb”).<\/li>\n
  12. Find string “Example TB” and replace it with the name of your TB (e.g. “My Studio TB”).<\/li>\n
  13. Replace all occurrences of string “en-GB” with the code for your source<\/strong> language (e.g. “de-DE” for German-Germany).<\/li>\n
  14. Replace all ocurrences of string “pl-PL” with the code for your\u00a0target<\/strong> language (e.g. “fr-FR” for French-France).<\/li>\n
  15. If you do import term base, remember to replace index languages (English, Polish) with your source and target languages.<\/li>\n
  16. Save edited “Import_wrapper.sdlproj” file. If you changed the extension in step 8, remember to re-name it back to .sdlproj.<\/li>\n
  17. Create a ZIP\u00a0archive of the folder (e.g. “Package”) content.<\/li>\n
  18. Rename the archive by changing .zip extension into .sdlppx<\/li>\n
  19. Import content to memoQ with “Import package<\/strong>” command. memoQ will notify you during import that there are no files to translate, but TM and\/or TB will be imported and can be used in different memoQ projects.<\/li>\n<\/ol>\n

    Please note that since\u00a0Import_wrapper.sdlppx file does not contain any files for translation, it can’t be imported into Studio. And if you have problems with changing file extensions, please see here<\/a><\/strong>.<\/p>\n","protected":false},"excerpt":{"rendered":"

    Tweet memoQ is great tool with many interoperability features, including easy SDLXLIFF file import\/export,\u00a0ability to import Studio packages and generating\u00a0Studio return packages. And while packages are imported with translation memories and term bases, strangely the ability to import stand-alone Studio TMs (SDLTM) and TBs (SDLTB) is nowhere to be found in the UI. And this … <\/p>\n

    Continue reading<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[6],"tags":[20,22,24,30,31],"_links":{"self":[{"href":"https:\/\/wasaty.pl\/blog\/wp-json\/wp\/v2\/posts\/872"}],"collection":[{"href":"https:\/\/wasaty.pl\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wasaty.pl\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wasaty.pl\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/wasaty.pl\/blog\/wp-json\/wp\/v2\/comments?post=872"}],"version-history":[{"count":1,"href":"https:\/\/wasaty.pl\/blog\/wp-json\/wp\/v2\/posts\/872\/revisions"}],"predecessor-version":[{"id":873,"href":"https:\/\/wasaty.pl\/blog\/wp-json\/wp\/v2\/posts\/872\/revisions\/873"}],"wp:attachment":[{"href":"https:\/\/wasaty.pl\/blog\/wp-json\/wp\/v2\/media?parent=872"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wasaty.pl\/blog\/wp-json\/wp\/v2\/categories?post=872"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wasaty.pl\/blog\/wp-json\/wp\/v2\/tags?post=872"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}