Is English (Europe) the new language on the other side of the Channel that we’ll all have to learn if Brexit actually happens… will Microsoft ever create a spellchecker for it now they added it to Windows 10? Why are there 94 different variants of English in Studio coming from the Microsoft operating system and only two Microsoft Word English spellcheckers? Why don’t we have English (Scouse), English (Geordie) or English (Brummie)… probably more distinct than the differences between English (United States) and English (United Kingdom) which are the two variants Microsoft can spellcheck. These questions, and similar ones for other language variants are all questions I can’t answer and this article isn’t going to address! But I am going to address a few of the problems that having so many variants can create for users of SDL Trados Studio.
There’s always been the occasional question appearing on the forums about data protection, particularly in relation to the use of machine translation, but as of the 25th May 2018 this topic has a more serious implication for anyone dealing with data in Europe. I’ve no intention of making this post about the GDPR regulations which come into force in May 2016 and now apply, you’ll have plenty of informed resources for this and probably plenty of opinion in less informed places too, but just in case you don’t know where to find reliable information on this here’s a few places to get you started:
With the exception of working under specific requirements from your client, Europe has (as far as I’m aware) set out the only legal requirements for dealing with personal data. They are comprehensive however and deciphering what this means for you as a translator, project manager or client in the translation supply chain is going to lead to many discussions around what you do, and don’t have to do, in order to ensure compliance. I do have faith in an excellent publication from SDL on this subject since I’m aware of the work that gone into it, so you can do worse than to look at this for a good understanding of what the new regulations mean for you.
I’m pretty sure that when we started to build the new Customer Experience Team in Cluj last year that there was nothing in the job description about being competitive… but wow, they are!!! I’d be lying if I said I wasn’t competitive, because I know I am, but it’s been a long time since I’ve had these kinds of feelings that keep me up at night.
To some extent I think the training requirements at SDL are the perfect fuel for this type of environment and I haven’t made up my mind yet whether it’s healthy or not. But in their roles the team speak with customers through the online chat, in the community, via email… basically anywhere anyone comes in with a question because they don’t have a support contract or an account manager to ask and they didn’t know about the SDL Community which is of course the best place to go for help. To be able to answer the variety of technical questions we see, all the team have either completed or are working through the various SDL Certifications available at a rate of knots and are learning more about the sort of problems faced by translators and project managers just by having to help people every day. They are doing a fantastic job!
In the years that the SDL AppStore has been around I get asked one question on a fairly regular basis… “How can I find out about new apps or updates to existing apps?”. A very reasonable question of course and one that has not been addressed particularly well, albeit there have been ways to keep yourself informed. The ultimate solution we all want to see is the AppStore embedded into SDL Trados Studio, but as that isn’t going to happen for a while here’s a couple of ways you can still keep yourself aware of the updates. The first is via twitter and this has been around for a while; the second is using an RSS feed which is brand new as of today!
It’s true… I’m a die hard desktop user. I love the benefits I get from my mobile phone, using dropbox, the benefits of machine translation, Netflix and all the cool things that come with being able to use online features in the cloud. But I’ve still been reticent to wholeheartedly embrace online technology and talk about it in this blog. When I ask myself why that is, the first thing that crosses my mind is the unreliability of online connectivity. Some people have a view of me as being a calm and patient person, and I do try hard to be that person, but when it comes to a lack of connectivity I turn into Mister Angry and Frustrated very quickly! So the very idea of working with solutions that only offer an online capability for everything leaves me cold. It’s one thing being unable to watch a film, share files, pick up my email or use my phone, but not being able to work at all is another thing altogether. If I was working as an independant translator with all the benefits that can bring of being able to work anywhere, then having a good offline capability would be essential. Studio of course offers me the offline capability, but today (and in a few more articles as there’s a lot to cover) I want to talk about the cloud and in particular SDL GroupShare. Many of you may wonder if this has any relevance for you, but hopefully you’ll see it does because the solutions SDL offer in this space give you the flexibility you need when working with the cloud and even as a freelance translator you may get asked to work in that environment. I’m going to tackle a few scenarios to explain, starting with creating projects. Continue reading “Cloud murmurings… part 1.”
Using stylesheets to enhance the translators experience when working with XML files can be very helpful and sometimes essential. It allows you to pull details from the XML and display them in a preview pane so that the translator has more context around the translatable text. It can also provide a mechanism for displaying text that you don’t want extracted from the XML for translation at all. This is nothing new of course and localisation engineers and experienced translators have been doing this for years. In fact I’ve even written about this in the past providing a simple example of how it’s done and some reading resources for anyone who would like to learn how. So why am I bringing this up again?
AdaptiveMT was released with Studio 2017 introducing the ability for users to adapt the SDL Language Cloud machine translation with their own preferred style on the fly. Potentially this is a really powerful feature since it means that over time you should be able to improve the results you see from your SDL Language Cloud machine translation and reduce the amount of post editing you have to do. But in order to be able to release this potential you need to know a few things about getting started. Once you get started you may also wonder what the analysis results are referring to when you see values appearing against the AdaptiveMT rows in your Studio analysis report. So in this article I want to try and walk through the things you need to know from start to finish… quite a long article but I tried to cover the things I see people asking about so I hope it’s useful.