I’ve always had a secret desire to be able to program computers… the problem is it’s not something you can do just like that! I can recall starting off with a Commodore PET 2001 some time in the late 70’s and I can remember how enjoyable it was to be able to create simple scripts that could react to whatever you pressed on the keyboard. I should have realised back then it would have been smart to focus on technology, but instead I took a bit of a detour in my career and computers didn’t feature at all until around 1987 when I was introduced to the HP41c from Hewlett Packard. This had very basic programming functions, a magnetic card reader and a thermal printer and I loved it! In fact I loved the way HP calculators worked so much I had an 11c for years until I dropped it trying to align a laser while being dangled headfirst into a catchpit on a construction site! And we think the Studio alignment process is tricky 😉
SDL Trados Studio is up to Studio 2017 which is the fifth major version since Studio 2009 was first released some eight years ago now. During these eight years I think it’s fair to say we have seen less and less requirement for the old Trados features, yet despite that we do see some interesting tools making an appearance in the SDL AppStore that mirror some of the old functionality. In fact some of these apps are quite recent and seem to have been driven by requests from users who miss some of the things you could do in Trados but still cannot do in the out of the box Studio solution. So I thought it might be fun to take a look at some of these apps and if you are one of those translators who remembers all the good things Trados could do… and can I say forgotten the things it could not… then perhaps you’ll find these apps useful!
A nice picture of a cutie cat… although I’m really looking for a cutie linguist and didn’t think it would be appropriate to share my vision for that! More seriously the truth isn’t as risqué… I’m really after Qt Linguist. Now maybe you come across this more often than I do so the solutions for dealing with files from the Qt product, often shared as *.TS files, may simply role off your tongue. I think the first time I saw them I just looked at the format with a text editor, saw they looked pretty simple and created a custom filetype to deal with them in Studio 2009. Since that date I’ve only been asked a handful of times so I don’t think about this a lot… in fact the cutie cat would get more attention! But in the last few weeks I’ve been asked four times by different people and I’ve seen a question on proZ so I thought it may be worth looking a little deeper.
There’s been a few ups and downs getting SDL Analyse off the ground, but it’s finally there and it’s worth it! If you have no idea what I’m referring to then perhaps review this article first for a little history. This app was actually released as the 200th app on the SDL AppStore in February this year, but in addition to the applause it received for its functionality there has been less positive aspects for some users that needed to be addressed.
But first, what does it do? Quite simply it allows you to get an analysis of your files without even having to start Studio, or without having to create a Project in Studio. If you’re a regular reader of this blog you may recall I wrote an article in 2014, and in 2011 before that, on how to do an analysis in Studio by using a dummy project. In all that time there has been only one app on the appstore that supports the analysis of files without having to use Studio and this is goAnalyze from Kaleidoscope. In fact goAnalyze can do a lot more than SDL Analyse but there is one significant difference between these apps that makes this one pretty interesting… you don’t require the Professional version of Studio to use it. But it’s also this difference that has been the cause of the ups and downs for some users since SDL Analyse was released. In order to resolve the problem of needing to use the Project Automation API, which needs the Professional version of Studio, the app needed to use a windows service that was hooked into Studio. For the technically minded we had a few things to resolve:
… in with the new!
Although I’m not part of the core support team anymore the knowledgebase has always been something that held a particular interest for me. When I joined SDL in 2006 we had two knowledgebase systems, each integrated into the support systems that were being used at the time. These were Salesforce and RightNow Technologies. The first big change I was involved in with regard to systems was moving the support teams onto one ticketing system and one knowledgebase. We wanted Salesforce as the ticketing system as it gave good visibility into the tickets being raised to everyone at SDL because Salesforce was being used as the CRM tool of choice. But in those days the knowledgebase component wasn’t great, so we adopted a new system. The system we chose was Talisma.
What a horrible name… lurkers! It carries all kinds of negative connotations from science fiction monsters to the stuff of nightmares where we think of spying and being followed by something or someone we don’t like. Of course I’m not using this term in these contexts so I better explain. I’m talking about communities and user participation, or more specifically about users who read and observe but rarely contribute to the conversations at all.
Community managers often think about user participation based on a 90:9:1 rule where 90% of users are referred to as lurkers who read all the activity but don’t contribute themselves, 9% contribute from time to time and 1% are pretty active and probably account for most of the contributions. I guess I can see why this negatively charged name is used, but in addition to being a horrible name it doesn’t really do justice to how important this group of community users are.
In 2013 I wrote an article called “Solving the Post-Edit Puzzle” which was all about finding a way to measure, and pay for post-editing translations in a consistent way. Then in 2015 I wrote another called “Qualitivity… measuring quality and productivity” that was all about everything Post-Edit Compare could do but then added many layers of detail and complexity through Qualitivity to support Quality Measurement including a TAUS DQF integration, and incredible metrics that are still not matched by any tool today that I am aware of, and are so good that they are often used to support academic research into translating and post-editing behaviour.
This is all great stuff and I have always been a huge fan of the work that Patrick Hartnett has done on all of the applications he developed over the years. You don’t often find experienced developers with indepth domain knowledge like this and his apps have always been really relevant to solving problems in the localisation workplace. So I wanted to bring up and discuss the app that was actually the predecessor to these great apps I just mentioned. It was also an app that was no longer supported once it’s first successor, Post-Edit Compare, was released. The app was released around 2011 I think and was called SDLXLIFF Compare.
It’s been a while since I wrote anything about the SDLXLIFF Toolkit.. in fact I haven’t done since it was first released with the 2014 version of Studio. Now that we have added a few new things such as SDLPLUGINS so that apps are better integrated and can be more easily distributed with Studio we have launched a new version of the toolkit for Studio 2017. What’s new? To be honest not a lot, but there are a couple of things that I think warrant this visit.
First of all, the app is now a plugin and this means it loads faster, is always available and there are a few tricks to being able to get the most from this. Secondly, there are a few fixes to the search & replace features that make it possible to complete tasks that Studio will fail with and to do this the API team completely rebuilt the regex engine. So whilst you won’t see too many changes, there are a few under the hood.
The best way to illustrate this is to show you so I have created a short video below where I have tried to explain how best to use the toolkit now it’s a plugin and not a standalone application, and I used the problems described below to demonstrate how it works. If you want to know what else it can do I have reproduced part of the original guide below the video as that seems to have been lost over the years. This might be helpful for a few of the more obscure features you may not have realised were possible.
Probably you’re all far more educated than me and when you read COTI you probably didn’t think “chuckling on the inside” did you? I googled it and looked at four acronym websites, none of which found the correct definition… but two of them returned the title of this article so it must be right!! Oh how I wish it was… just to bring a little levity to the ever so serious tasks of interoperability. But no, it stands for Common Translation Interface (COTI). This is a project pioneered by DERCOM which is the “Association Of German Manufacturers Of Authoring And Content Management Systems”… so nothing to be amused about there!
The subject of interoperability is in fact a serious one and many tools like to claim they are more interoperable than others as a unique selling point for anyone prepared to listen. It’s also a big topic and whilst I am always going to be guilty of a little bias I do believe there isn’t a tool as interoperable as the SDL language Platform because it’s been built with support for APIs in mind. This of course means it’s possible for developers outside of SDL to hook their products into the SDL Language Platform without even having to speak to SDL. Now that’s interoperability! It’s also why I probably hadn’t heard of COTI until the development was complete and I was asked to sign a plugin for SDL Trados Studio by Kaleidosope… outside of SDL I think they are the Kings of integration between other systems and the SDL language portfolio.
“More power to the elbow”… this is all about getting more from the resources you have already got, and in this case I’m talking about your Translation Memories. In particular I’m talking about enabling them for upLIFT. upLIFT, in case you have not heard about this yet despite all the marketing activity and forum discussions since August this year, is a technology that is being used in SDL Trados Studio 2017 to enable some pretty neat things. I’m not going to devote this article to what upLIFT is all about as Emma Goldsmith has written a really useful article today that does a far better job than I could have done. You can find Emma’s article here, called “SDL Trados studio 2017 : fragment recall and repair“. But a quick summary to get us started is that upLIFT enables things like this:
- fragment matching
- whole Translation Units
- partial Translation Units
- fuzzy match repair
- from fragment matching
- from your termbase
- from Machine Translation