Once upon a time, of course, the translation environment was just black and white with gray in between. Black and white and gray? The AppStore gods were understandably bored and angry, so they went looking for other colours to brighten the world for their users. The resulting colours emerged from the Microsoft Word palette resulting in fifteen colours to choose from. The AppStore gods were so happy with these colours they decided to paint the translation environment from the AppStore. They opened Visual Studio and flung the colours around, resulting in a brand new app. they called “Wordlight” and a new colourful feature for the “Community Advanced Display Filter”.
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:
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.
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
When I write these articles I always start with thinking about the image at the top. I do this for two reasons, the first is because it usually helps me think of some bizarre introduction (like this!) that helps me start writing, and the second is because every now and again I like to play around with Gimp which is the free image software I occassionally use. It’s always nice to spend a little time doing something frivolous because it’s good thinking time without being distracted by the job! I don’t really know how to use this software at all, but it’s fun seeing what turns out… and I confess I often use a combination of powerpoint and Gimp simply because some things are just easier in powerpoint! Eventually I might actually learn how to use it properly… I’ll keep practicing anyway.
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…”
It could be said that translators come into the industry for the love of language, and the creative nature of the work, writing beautiful translations that at least do justice to the original texts. It might even be true for many… but let’s face it, very few people can afford to do this for a full career without thinking about the money! So it’s all the more surprising to me that translation vendors don’t provide a mechanism for dealing with the money in their toolsets. Sure, you can have an analysis that can be used as the basis of a quote or an invoice, but you don’t see anywhere that deals with the money! The larger Translation Management Systems have features for doing this, or they integrate with larger Enterprise systems for accounting and project management, but what about the translators? How do they manage their business?
Well… there are applications on the SDL AppStore that can help with this in some ways. For example:
- SDL InQuote – an interesting, sometimes problematic application, that can allow you to create quotes and invoices based on the analysis files in your Studio projects
- Post-Edit Compare – a wonderful application that in addition to carrying out a post-edit analysis of the work you are doing can put a value to it based on your rates. But it doesn’t create quotes or invoices.
- Qualitivity – another wonderful application that in addition to tracking just about everything you do in Studio can put a value to it based on the post-edit analysis or on a time basis. But it doesn’t create quotes or invoices either.