Every time a new release of SDL Trados Studio is released there are usually a flurry of blogs and videos explaining what’s in them, some are really useful and full of details that will help a user decide whether the upgrade is for them or not, and others are written without any real understanding of what’s in the software or why the upgrade will help. That’s really par for the course and always to be expected since everyone is looking for the things they would like to meet their own needs. So for me, when I’m looking for independent reviews of anything, I find the more helpful reviews give me as much information as possible and I can make my own mind up based on the utility I’ll get from it, the fun in using it and the cost of upgrade. I put a couple of what I would consider helpful reviews here as they both try to cover as many of the new features available as possible. So if you are in the early stages of wondering at a high level what’s in it for you then you could do a lot worse than spending 10 or 20 minutes of your time to read/watch the contributions from Emma and Nora below.
In the last year or so many articles have been written about XLIFF 2.0 explaining what’s so great about it, so I’m not going to write another one of those. I’m in awe of the knowledge and effort the technical standard committees display in delivering the comprehensive documentation they do, working hard to deliver a solution to meet the needs of as many groups as possible. The very existence of a standard however does not mean it’s the panacea for every problem it may be loosely related to. It’s against this background I was prompted to write about this topic after reading this article questionning whether some companies were preventing translators from improving their lives. The article makes a number of claims which I think might be a little misguided in my opinion… in fact this is what it says:
XLIFF 2.0 is a “new” bilingual format for translation that attempts to do a handful important things for translators.
- Improve the standard so that different translation tools makers, like SDL, don’t “need” to create their own proprietary versions that are not compatible with other tools
- Creating true interoperability among tools, so translators can work in the tool of their choice, and end-customers can have flexibility about who they work with too
- Allow businesses to embed more information in the files, like TM matches glossaries, or annotations, further enhancing interoperability
I say “new” because XLIFF 2.0 has been around for years now. Unfortunately, adoption of the XLIFF 2.0 standard has been slow, due to tools makers and other players deciding that interoperability is not in their interest. It’s one of those things where commerce gets in the way of sanity.