… and this will be particularly good news for users working in SDL Trados Studio with SDL WorldServer. Today the Glossary Converter was updated on the OpenExchange with a number of very cool enhancements. These are support for users still working with SDL MultiTerm 2009, support for Microsoft Excel workbooks containing multiple worksheets, Spanish user interface, a number of smaller usability improvements and bugfixes and the one I’m most interested in here… support for TBX. TBX is a TermBase eXchange format that was developed for sharing terminology between different tools. The reason I’m so interested is because if you want to use a TBX file in Studio as a resource for your AutoSuggest then you have to use MultiTerm Convert in order to create a MultiTerm TermBase. This is not too difficult, but it can take a little work if there is a complex structure in the TBX… and of course it can take a little while as it’s at least a two-step process. So making this easier would be great.
When I started writing this blog the first article I wrote was about the SDL OpenExchange. I thought I’d start this year off by sharing my favorite applications … my favourite FREE applications. We had a fair few of these over the course of the year but I’ll pick out six that I think are well worth a look. In no particular order (well… alphabetical order) these six are:
- Glossary Converter
- Package Reader
- SDLXLIFF Compare
- SDLXLIFF to Legacy Converter
Updated January 2015 : Also possible, and easier, to use the Variable Manager from the SDL OpenExchange for this.
I mentioned in a previous post that it wasn’t possible to import long variable lists into a Studio Translation Memory using the desktop version of Studio. You can do this with GroupShare, but the ability to do this in the desktop version is a work in progress.
Well that wasn’t quite true and as I’ve been preparing for some roadshows and events that are coming up this month I figured out a simple workaround using SDL Trados 2007 Suite.
Update: 15 January 2015
This is now possible for all file formats except for ITD, updated in Studio 2014.
SDL Trados Studio 2011 SP2 has introduced “edit source”… but only for Microsoft Word and Microsoft PowerPoint file formats at the moment. For Freelance Translators this is a welcome addition because it has been one of the most heavily voted for ideas on the SDL Ideas site. However, is this enough and why haven’t SDL introduced this before? This is fast becoming a topic for much debate on the public forums and Facebook pages so I thought it warranted a little insight into the problems of introducing “edit source”.
The new Studio product and the old Trados products are compatible aren’t they? Would it be true to say that Studio can handle the old Trados formats, but Trados can’t handle the new Studio formats out of the box? I think it’s true… but it still requires a little knowledge about how best to handle the compatibility issues that might arise.
This is only the second blog I’ve written and the early dliemma is what to write about first. I decided to talk about the OpenExchange (rebranded later in 2016 as the SDL AppStore) created by SDL as this is an industry first and in my opinion is a very strong reason to buy into the Studio platform this is created for.