The most viewed article I have ever written by far was “So how many words do you think it was?” which I wrote in 2012 almost ten years ago. I revised it once in 2015 and whilst I could revise it again based on the current versions of Trados Studio I don’t really see the point. The real value of that article was understanding how the content can influence a word-count and why there could be differences between different applications, or versions of the same application, when analysing a text. But I do think it’s worth revisiting in the context of MT (machine translation) which is often measured in characters as opposed to words… and oh yes, another long article warning!
Growing a product range, buying new companies, being bought yourself, adopting new technology, reorganising etc… all of this creates significant change across an organisation that often feels as though you’re on a merry-go-round where things change as you go around until you’re back to where you started and then it all changes again. I can only imagine that feeling applies to customers and employees alike as each revolution strives to be better than the last, easier to navigate, meaningful in its purpose and full of the promise of success once properly implemented… and yet slightly confusing at the same time!
Why would you have to? Surely Ai can translate itself? If not it sounds like a pretty big topic… or I’m just confused. Acronyms can do this to you and these days we do have good reason to be confused… Multiterm/Machine Translation (MT), National Aeronautics and Space Administration/North America South America (NASA), Role Playing Game/ Rocket Propelled Grenade (RPG), Wages For Housework/Working From Home (WFH)… the latter essentially being the same!! The list is huge and these days I find myself looking something up almost every day. Ai is another one… Artificial Intelligence is probably what crossed your mind right from the start, particularly since I put it on top of a brain! I actually found 164 meanings for this acronym but only one of them matches the topic for my article… and that is Adobe Illustrator which should be a far more manageable topic for translation!
This year at the Spring Trados Roadshows the emphasis was firmly placed upon education. Almost all the presentations were based on providing translators, project managers, localization engineers etc. with great material to help them as they work with the Trados toolsets.
I had a few presentations at this event and decided it might be useful to post a few of them here, especially the ones that might help with some of the common filetype questions we see in the communities from time to time.
Time seems to be going faster as I’m getting older as it doesn’t seem that long ago since we saw the release of the 2019 version of SDL Trados Studio. But here we are, it is that time again and many users will already have noticed they have a shiny new version in their account… SDL Trados Studio 2021. Fast as it is, we don’t want to do these product launches too often because I can tell you it’s a major undertaking requiring no small amount of coordination between the product management teams, core development teams, AppStore team, support teams, customer success teams, marketing teams, sales teams, back office teams, IT teams, 3rd party developers who provide plugins and more. In addition to this we often have other projects on the go and many of the teams worked on the new sdl.com website which also went live this week, AND everyone did all of this while having to work isolated from their colleagues while working from home. Quite an achievement and I certainly feel proud to be part of this SDL team, and not just because of how well they all work together.
The Old Farts Language Code Club! This is a new club, inspired by a comment in the SDL Community from a prospective member. I’m not sure yet of the age at which you can qualify for membership, but in addition to the age requirements, which may have stringent rules to prevent any young whippersnappers from joining, it’s essential that prospective members have a good grasp of the language codes used in Trados Studio. I’m also not sure of the demand, so I may open a waiting list that could include anyone who already makes good use of the language codes in Trados Studio but isn’t an old fart yet!
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
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.
Studio 2019 has arrived and it brings with it some nice features on the surface, and some important improvements under the hood… but it also brings with it a lot more upgrades than just Studio, and I don’t just mean MultiTerm! The SDL AppStore is one of the unique benefits you get when you work on the SDL technology stack and there are hundreds of apps available that can provide additional resources, custom filetypes, file converters, productivity enhancements, manuals, etc. When you upgrade your version of Studio you are also going to have to upgrade your apps. Many of the apps are maintained by the SDL Community team and these have all been upgraded ready for use in Studio 2019, but the majority have been created and maintained by others. I’ve written this article to explain what you need to look out for as a user of SDL Trados Studio or MultiTerm, and also as a reference guide for the developers who might have missed the important information that was sent out to help them with the process. Continue reading “Upgrading apps in the SDLAppstore…”