“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
So it’s really a pretty cool thing that is also another AutoSuggest Provider, so you can enter the fragments as you work just by typing what you see. Now, this leads me into what I’d like to talk about first, before I get to preparing your Translation Memories, and that’s how to make the most of what’s become a very busy interface with information potentially coming from all over the place. It’s not immediately obvious how useful the Fragment Matching can be as the windows are quite small on a single screen but with a little elbow grease before you start you can find the best solution for you. To demonstrate this I have prepared a quick video showing how to move the windows around to get what you want.
Arranging your View Parts
Video: Approx. 4 minutes running time
Now that we have the interface as we like it let’s come back to the knub of this article. Preparing your TMs for upLIFT. Out of the box, as Emma explained, you have to go through a three step process:
- Turn on the Fragment Alignment Status
- Build the Translation Model
- Align the translation units
You have to do this to enable fragment matching. If you want to know more about why then I highly recommend you take a look, or join the discussion, in this thread in the SDL Community. The principal developer of upLIFT in Studio is discussing how it works and answering some interesting questions from Studio 2017 users.
If you never import a TM into your TM, or merge TMs then you probably won’t need to do this preparation exercise again as the TM is updated automatically in realtime after this. But if you do any merging or importing then you will have to repeat the process to prepare the additional TUs that have not been added while working with Studio 2017.
Now, that in itself is not too bad… but what if you have twenty, or a hundred Translation Memories? Then it becomes quite a process as you can only do one at a time, and as you do this you can’t use Studio for anything else. So set aside an evening, or a weekend, when you are not doing anything else to tackle the Translation Memory preparation tasks! And before you start go and download ReindexTMs from the SDL AppStore. This app was first introduced when we released Studio 2014 SP2 and introduced the concept of Alphanumeric placeables. It allowed you to reindex multiple Translation Memories to support this enhancement in one sitting by automatically carrying out the process that you would otherwise have to complete, one Translation Memory at a time, in Studio. For Studio 2017 the AppStore team have enhanced this little app and converted it to an sdlplugin and added the capability to run the upLIFT process for multiple Translation Memories in one go.
I thought the best way to show you how to do this was with a demonstration, so I took six Translation Memories, created courtesy of the DGT, and prepared them for upLIFT in one go. The process is in the video below… I hope it’s helpful.
Video: Approx. 10 minute running time