3. AutoSuggest and Automatic Translation

AutoText and AutoSuggest
In Word, and also in later versions of TagEditor, there is a function called AutoText. The AutoText entry in Word can be accessed in two ways; a) typing the first four letters of the word makes a suggestion displayed below the segment b) entering the abbreviation you have chosen and then push F3. You can enter new AutoText entries in the glossary by highlighting the word and push Alt+F3. The glossary can also be edited separately.
In the Studio AutoText abbreviations are not used, so you always have to type the four first letters. And it is not possible to add AutoText entries on the fly, you have to use Tools/Options/AutoText, and enter the words one by one. I have not yet found any method of separately editing an AutoText file. If that is possible, it would be nice to compile a list or even import the AutoText entries already prepared in Word. There is an import/export function in Studio's AutoText, so it is probably possible, if you can find software that is able to edit the file type.autoTxt.
AutoSuggest
One of the new functions in Studio is AutoSuggest, but it is not included in the Freelance version, you have to buy a separate license. When typing, the AutoSuggest functions like AutoText as above. The difference is that the AutoSuggest glossary entries are context dependent, so only words that AutoSuggest believes you will use in the segment are displayed. And that is exactly what makes the function so useful!
The AutoSuggest glossary is generated by processing a translation memory that has to hold at least 25 000 TU: My memory for English into Swedish was a little larger than 400 000, the maximum recommended value, and the result was very good. There is also a possibility to download AutoSuggest glossaries from SDL, but not in my language combinations (Eng>>Swe. Fin>>Swe and Ger>>Swe).
The AutoSuggest is actually a very useful function, especially in Swedish, as we often have very long words. And, the AutoSuggest creation includes not only commonly used single words from the TM, but also short often used phrases. It is also case sensitive, which is nice as I sometimes get the first part of standard phrases from the suggestion.
And, you of course also get the terms from your MultiTerm glossary in the same drop down box below the segment. As I have saved all special terminology and customers glossaries from all projects during the years in my MultiTerm, this is also a powerful resource.
The AutoSuggest gets terms from three sources; the AutoText glossary, your AutoSuggest compiled from translation memory and from MultiTerm.
Automatic Translation
In old Trados, you get suggestions for translations in the target window for exact and fuzzy hits. That is of course the same in studio, but you can also add suggestions from the SDL Automated translation server. There is a version for English into Swedish, but not for my other language combinations. The connection to the server is fast and stable, there seems to be very few delays, save the opening of the first segment, which takes a few seconds. Most of the suggested translations are of course useless, and would take more time to edit than to rewrite. But in some cases, about 1 of 10 sentences I choose the suggestion and edit. In a very few cases I get a complete sentence that only have to be slightly corrected. And, the database quality could be improved; there are even misspelled words in the suggested sentences.
In rare cases you get a hit like this in the Automatic Translation:
Source:
If a solution with necessary concentration is available and can be transported without problems to the plant, it can be used.
Automatic target:
Om en lösning med nödvändig koncentration finnaer till hands och kan transporteras utan problem till plantan, kan användas det.

Ok, there are errors, but definitely so few that it is worth editing. And I see a possibility to development here: I think it would be relatively easy to combine the SDL Automated translation server with a technical vocabulary that explains the fact that plant mostly is anläggning. The "finnaer" seems to be a misspelled word in the database that could easily be corrected.

But there definitely is a future for this kind of translation support, and it is actually useful at least for the type of text I work with. So I will definitely have it up and running.
I believe that the combination of the new support functions in Studio already is boosting my productivity, and will do even more, as I get used to this new way of combined typing/selecting/editing.