And the idea of translating in a browser seemed dubious to me, and it remains so in many scenarios that are relevant to my work. I looked at it briefly in the early days and was unimpressed: too limited, I thought. The least among these tools was, in my consideration, the web-based Wordfast Anywhere (WFA). It would not surprise me if much of the loyalty I find among users of Wordfast is inspired by the personal qualities of Yves as much as by any technical features of his tools.
That issue is solved in the meantime, so I suspect I might not be quite so unhappy were I to revisit the application.īut really, Wordfast doesn't come onto my radar very often, and when it does, it's not so much the application suite itself as it is the Wordfast creator - Yves Champollion, who follows in a way the family tradition of the famous French Egyptologist, Jean-François Champollion, translator of the Rosetta Stone, and who has earned his own fair share of praise for his many years of support for individual translators and their professional organizations.
When Wordfast Pro came along, I was disappointed in the interoperability of its early versions and it being late to the party for supporting XLIFF formats (as were some other popular tools). Wordfast Classic (back when it was the only Wordfast app) was brought to my attention by an enthusiastic manager of a German bank's translation team more than 15 years ago he found that the " blacklist" feature for terminology (since adopted by others - for example in memoQ's "forbidden" terms) was extremely helpful to his translators in avoiding terms which might provoke branding controversies or which were simply inappropriate in a particular specialist context. Studio 2011 SP1 & Trados 2007 bilingual files (DOC or TTX) – Part II ( Wordfast suite of applications has a long history, and through much of it I've had my eye on the tools but up to now never really found them up to the demands of my work.Studio 2011 SP1 & Trados 2007 bilingual files – Part IV ().Studio 2011 SP1 & Trados 2007 bilingual files (DOC or TTX) – Part I ().
Studio 2011 SP1 & Trados 2007 bilingual files – Part III ().
You can now proceed to review the files, to update your Studio TM or to finalize your project as usual. Use the Import tab to load the bilingual files you received from your providers and click on Start Processing to import the translation into the original SDLXLIFF files. STEP 4: CONVERT THE TRANSLATED FILES BACK TO SDLXLIFF tmx files are based on XML and could be translated in many CAT tools or in TMX editors, such as Olifant. docx can be translated under Trados 2007 or using Wordfast Classic for instance, TTX files are supported by many Cat tools, such as TagEditor, MemoQ, Wordfast Pro and many more.
STEP 3: GET YOUR BILINGUAL FILES TRANSLATEDīilingual. Then, choose the target format in the drop-down list ( bilingual. You may load files or complete Studio projects. STEP 2: LOAD SDLXLIFF FILES AND EXPORT THEM TO THE FORMAT OF YOUR CHOICE Under Tools > Settings, decide which segments you want to export and import (Perfect matches, Context matches, etc.).Īnd define which status the imported segments should adopt after the import process (draft, approved, etc). Thanks to this tool, we can say that finally Trados 2007 and Studio are (almost) completely compatible with each other. Once you receive the translated files, you just need to import them into your original SDLXLIFF files. Your providers can now use Trados 2007 or other translation environments to translate your Studio projects. Thanks to this very useful tool from Logos you can convert your Studio SDLXLIFF files to four different bilingual formats: bilingual. But here’s the perfect workaround!Ī new App has recently been released on the SDL OpenExchange platform: SLDXLIFF to Legacy Converter.
Downgrading to Trados 2007 would imply exporting the TM from Studio, probably loosing segments on the way, and getting a lower leverage due to segmentation or tag issues. Well, a few months ago, you would have been obliged to take a step back and to prepare your project in Trados 2007. Suppose that you use SDL Trados Studio but your providers still use Trados 2007 or other CAT tools. Scenario: You use Studio but your providers still use Trados 2007