The workaround is neither guaranteed nor supported (as the SDL article makes clear). But since it seems to work, it might extend Trados 'classic' usefulness on newer machines. For detailed instructions, see the following instructions (suggested by SDL's original article: ' SDL Trados 2007 Suite toolbar compatibility with Microsoft Office 2010', article # 3359): To use Trados 2007 toolbar with Microsoft Office 2010, hook up Word 2010 with SDL Trados Translator's Workbench 2007, as follows: • Make sure that Trados, MultiTerm and Microsoft Office (Word, Outlook, etc.). Are not running • Find the file Trados8.dotm in the folder C: Program Files SDL International T2007 TT Templates. • Copy Trados8.dotm into the following folder: • Windows XP: C: Documents and Settings [USERNAME] Application Data Microsoft Word Startup • Windows Vista or Windows 7: C: Users [USERNAME] AppData Roaming Microsoft Word Startup • If the folder already contains a Trados8.dotm file, overwrite it • Find the file MultiTerm8.dotm in the folder C: Program Files SDL SDL Multiterm Multiterm8 Templates.
• Copy MultiTerm8.dotm into the following folder: • Windows XP: C: Documents and Settings [USERNAME] Application Data Microsoft Word Startup • Windows Vista or Windows 7: C: Users [USERNAME] AppData Roaming Microsoft Word Startup • If the folder already contains a MultiTerm8.dotm file, overwrite it. Start Microsoft Word 2010. You should now see, and be able to use, Trados's Workbench or MultiTerm from Microsoft Word 2010.
Update I've updated this post, adding the above detailed instructions, since the link to SDL's article was not working properly. Pablo, Riccardo: go to talisma.sdl.com and in the search field in the upper left corner type 3359 - that opens the article in question. I've noticed another issue with SDL Trados 2007 Professional and Microsoft Office 2010 Professional Plus.
At the moment, I'm translating fairly simple doc files (doc, not docx). I'm unable to move to the next segment with the standard shortcut of Alt+Num+. It simply does nothing. As a workaround, I use Alt+End, Alt+Home, but that's rather inconvenient.
The commands in this section are a useful addition to many CAT tools, e.g. SDL Trados (including SDL Trados Studio and Trados 2007), memoQ, Memsource. And Marching Black Ants are special formatting properties that can be applied to text in Word documents to indicate that it should not be translated by Wordfast. SDL Trados Studio 2009 Professional is the complete. Install or upgrade to SDL Trados 2007 Suite. 1 SDL TRADOS STUDIO 2009 INSTALLATION GUIDE SDL. Sdl Trados 2007 Suite Professional Property. Scriptcase Keygen Download Torrent. SDL Trados 2007 Suite - Installation Guide - Free download as. Through its integration with SDL Trados 2007 Suite.
Have you encountered such a behaviour or have any idea how to ger rid of it? I checked the keyboard shortcuts in Microsoft Word, and Alt+Num+ is assigned to the appropriate Trados function - but it doesn't work. Take care, Krzysiek. Hi Monika, As regards Visual Basic, I think the necessary file should be installed by Trados during installation.
But I'm afraid I have no idea how to solve the Visual Basic error message (Office 2010 after all is not officially supported by SDL for Trados 2007). I have found something on the Web: that seems to mention the issue - but since I have not experienced this particular issue myself, I cannot say if it works in all cases or not. Anonymous These are excellent instructions. But if this doesn't work for you(and all else fails), just REMOVE Trados completely, then RE-INSTALL again. Be sure to return the license key before you do that, if you have no extra key available(you can check liscense status at 'My account' page at sdl.com). Unicdma Software Free.
In my case, copy & paste Trados file in Word folder worked when I tried on previous Word versions, but not on Word 2010. After getting so many error messages(arrgghh!!), I just removed and reinstall Trados and it worked like a charm!(oh, and after re-installing Trados, make sure to check 'options' - 'show hidden text' so that you wouldn't panic that source text 'disappeared' in unclean file). Good luck, everyone!
============================================= To answer 'anonymous' above: Translator's workbench doesn't start automatically. You have to do it yourself. Just click 'Workbench' icon and it'll appear.
Anonymous Thank you so, so, so, so much! Thanks to you I've got Trados 2007 working with Word 2010 and I can finally get back to work after a day of tearing my hair out. Strictly speaking it should be up to SDL, or the agencies we work for (and who more or less force us to get Trados), to provide these instructions, but unsurprisingly they don't care enough to do so. It's left to individuals like yourself to take the time and effort to help the rest of us, and although that's not how it should be, I am extremely grateful! Hi Stefanie, Are you sure you have 64 bit word? I'm asking because when I updated my computer (to a new Windows 64 machine), the version of office that came with it was still 32 bit - so Trados 2007 could work with (almost) no problem with Office 2010.
The way to check in Word 2010 is to go File >Help >About: on the right you'll see information about the version of word (including whether it's 32 or 64 bit). If you do have a 64 bit version of Word, I believe there is little than you can do. Apart installing a different one.
With Office 2010 you can have two versions of Office side-by-side on your computer, so you could install Word 2003 and still keep Office 2010 (though i believe it would be better to install first the older version and then the newer one) - so long as you keep the different installations in different folders. Stefanie Mueller Hello Riccardo, Thanks for your speedy reply. Yes, I do have the 64 bit version of Word, but I am now considering 'downgrading' to the 32 bit version so I can run Trados 2007 which is the program I am more familiar with. During my research, I came across the SDLXLIFF to Legacy Converter which is available on the SDL Open Exchange website (With it, you can convert any SDLXIFF file to a segmented Word file. It works, I tried it out. Regards, Stefanie. I haven't tried to use Trados 2007 with MS Word 2013, but I'm not surprised if Trados 2007 doesn't work with Office 2013: after all it's a program that was last updated about six years ago, and if it relies on features of MS Word that have been changed in the last version, then it won't work any longer.
As far as i know, Studio works without problems with MS Word 2013 files. My suggestions: 1) If you have a computer with Windows 7, install XP Mode (I believe it is still available from Microsoft).
If you are on Windows 8, or in any case if XP Mode is no longer available, procure a copy of Windows XP, then install it on a virtual machine on your computer (there are several different programs that permit you to install a virtual machine - but you have to provide the operating system to install on the virtual machine yourself). 2) Once you have your virtual machine up and running (Windows XP mode, or another virtual machine, install in the virtual machine your old copy of MS Office (up to Office 2010 - but Office 2003 would do perfectly). 3) Install in the virtual machine Trados 2007. Depending on the virtual machine, the installation might go without a hitch, but in case it doesn't, I believe that SDL support should be able to help you (SDL support is available free for installation and licensing problems). A (perhaps) simpler alternative would be to use TagEditor (even without the preview) for customers that really insist on old-style Trados, and to use SDL Trados Studio (a much better program) for all other work. Good answers from Riccardo. The only thing I'd add is that if you have installed the 64-bit version of Word as well then this would immediately cause you a problem.
This is a problem for many Word plugins that have not been made 64-bit compatible and Microsoft themselves will recommend you use the 32-bit version of Office (on a 64-bit system, so this is fine) if you have any old toolbar plugins that you need to use regularly. If you already have a 32-bit version installed and it doesn't work then it may be that Office 2013 is a step too far for a product this old. Trados 2007 is already not supported anymore, and the Suite version (that is sold with 2011 as an option) will be the next to go. Certainly we won't do any more work on it to ensure it works with the latest versions of Windows and Office.
So in Office 2010 32-bit edition it all works fine. But I really have no idea about Office 2013. The solution, if you have to use Word bilinguals would be to create them in Workbench and then translate them in Studio. So don't use the Trados toolbar in Word at all anymore. I guess the solution if you want to continue having access to a Trados toolbar in Word solution is keep your old computer when you buy a new one or don't upgrade Windows/Office or keep a machine running the older Windows and older Office versions (or even install a Virtual machine for this). Having said that there is bound to be someone who figures out a way to make it work, there always is. So perhaps try the ProZ forums, or TW_Users as there are many experienced users who regularly upgrade their computers but still manage to work with the older tools!
It may be different on your computer, depending on your configuration, but it should be C: Program Files (x86) SDL SDL MultiTerm MultiTerm[x], where [x] is the number of your MultiTerm version (MultiTerm8, MultiTerm9, or MultiTerm11, for example). In fact, depending on which versions of Trados you installed on your computer, you may have several different folders: C: Program Files (x86) SDL SDL MultiTerm MultiTerm8 C: Program Files (x86) SDL SDL MultiTerm MultiTerm9 C: Program Files (x86) SDL SDL MultiTerm MultiTerm11. Trados8.dotm works ok with Trados7, Office 2010 32 bits and Windows 10 (it will not work with a 64 bits-version of Word) - After many hours of googling and reading all these posts here and elsewhere, I found that it is still possible to work with Trados 7:-). Good old Trados 7 that is simple for Word documents translation and avoids all those packages and projects concepts of modern tech translations in columns:-) - Good old fashion translation where translation knowledge counts more than code-related issues for the Web reader is still possible.
And yes, even works with Multiterm 2014 integration! For details or help on this contact me on mfcmachado[at]hotmail.com. By the way, so that you don't think I am old that old fashioned.
I do use Trados Studio 2014 and MemoQ2014 R2, but only when I have to for Web projects. I DO NOT like working in columns - not sure who really does but no one asks translators opinions anyway. Techis decide and we the translators have to be like sheep and bow. So for clients that 'only' want good translations in plain old Word formats, it is still possible to use the simple Word interface with Trados and make good use of a Multiterm database.