Every year I’m lucky enough to attend a few industry conferences which always provide an excellent environment for gathering feedback, spending time on a one to one basis with people working in the industry and generally getting a reality check on the things I do on a day to day basis. It’s true that I spend a lot of time working in the SDL Community where I do get exposed to the sort of problems people are trying to solve, but it’s really not the same as the exposure you get at a conference, especially if you attend with an open mind and a willingness to learn. So I always look forward to attending the few events each year that I do.
How do you eat an elephant? Well, of course we don’t really want to eat an elephant, we love elephants! But if we did want to eat something that large we’d do it in bite sized chunks! This is something that is particularly relevant when working with large resources such as translation memories or terminology that is freely available from a number of places on the internet. I’ve addressed this before in various articles… these two are particularly relevant to the topic I’m addressing today:
I can remember being asked in early 2007 to organise a report on the benefits of Passolo compared to other tools that also supported visual software localization. In the same year, shortly after that, SDL purchased Pass Engineering and SDL Passolo was born. At the time I didn’t know a lot about Trados Workbench or SDLX either as I had a very different role, and I only started getting interested in the technology we (and our competitors) use in 2008 just prior to the release of SDL Trados Studio 2009 the following year. In all that time since then, until a few months ago, I’m ashamed to say I’ve never taken more than a cursory look at it. It’s taken a course I’m doing at the moment at the University of Strasbourg to really bring home the value. One of the modules on this course is “Localization of Graphical User Interfaces” and under some expert tutorage I’m plugging many of the gaps I have in my knowledge of this industry. I’m even putting it to good use in my daily work!
When I started to look at the subtitling industry little did I know just how fragmented it would be! For years we have talked about SRT and yet when I look at the filetypes that tools like Subtitle Edit claim to support I find over 200! Normally I’m not a big fan of standards but that’s probably because I live in a world where there is little variation and supporting different bilingual files is trivial in comparison. But if there was ever a good argument for one it would be here! Asking people what format they see most often does help to narrow it down, but as we often find when developing software, the interest usually comes after the event and not before! So what formats can a translation tool support today?
Ever since the release of Studio 2009 we have had the concept of Language Resource Templates, and ever since the release of Studio 2009 I’d risk a bet that most users don’t know what they’re for or how to use them. To be fair this is hardly a surprise since their use is actually quite limited out of the box and access to the goodies inside is pretty hard to get at. It’s been something I used to see users complain about a long time ago but for some years now I rarely see them mentioned anymore. This article, I hope, might change that.
The origin of Chad (if you’re British) or Kilroy (if you’re American) seems largely supposition. The most likely story I could find, or rather the one I like the most, is that it was created by the late cartoonist George Edward Chatterton ‘Chat’ in 1937 to advertise dance events at a local RAF (Royal Air Force) base. After that Chad is remembered for bringing attention to any shortages, or shortcomings, in wartime Britain with messages like Wot! No eggs!!, and Wot! No fags!!. It’s not used a lot these days, but for those of us aware of the symbolism it’s probably a fitting exclamation when you can’t save your target file after completing a translation in Trados Studio! At least that would be the polite exclamation since this is one of the most frustrating scenarios you may come across!
At the start of this article I fully intended this to be a simple description of the problems around saving the target file, but like so many things I write it hasn’t turned out that way! But I found it a useful exercise so I hope you will too. So, let’s start simple despite that introduction because the reasons for this problem usually boil down to one or more of these three things:
- Not preparing the project so it’s suitable for sharing
- Corruption of a project file
- A problem with the source file or the Studio filetype
There are three things that have stood out for me this year. The first is how much support SDL have provided to their users to make sure they are able to work successfully with their investment. The second is how little many users are aware of this, and the third is just how many users have used Trados for a decade or more and were not aware of what a support & maintenance contract can bring you. This last one has been the biggest surprise to me as I’ve spoken to people who thought a support contract was more than the cost of the software; to people who thought it was support only and to people who didn’t know SDL provided any support at all! So, one of my resolutions for 2019 will be to try and make sure that all our users are more aware of how to get help, even if they don’t want to purchase a support & maintenance contract. So, I’ll cover these things:
- Support & Maintenance Contract
- SDL Community
- The Customer Experience Team
- The SDL AppStore Team
- The SDL Marketing Team
- Customer Experience Program