Michael Farrel’s IntelliWebSearch (IWS) is an extremely popular program for looking up terms in a large number of terminology (and other) resources, also from within Studio and other CAT tools. It’s quite easy to use, but the help pages (on the net) may be slightly off-putting. Therefore, I have written this quick guide, which will help you use the basic functions (which as usual is what you will use most of the time).

Note: This guide is about Version 3 of IWS. In 2015, however, Michael released Version 5, which is substantially improved in many ways, but which also is not free (although you might argue that €25 for a twelve-month license is not an awful lot of money; besides, you can test it for free during two months).

And eventually, there will be a guide to Version 5 on this website, similar to this one.

In brief: With IWS – both versions – you select a word or expression in your text and the either uses the shortcut Ctrl+Alt+B which will take you to the search window, where you can choose one or some (or all) of the web sites – up to 50 in Version 3 – which you have selected as suitable search places. Or you can enter a shortcut directly to a selected site (which may be preferable, since this directness is one of the great advantages of IWS).

Once arrived at the site you might find a suitable translation, in which case you select it and press Ctrl+Alt+C. The text will be copied and at the same time you are taken back to Studio (or wherever you started), where you can paste it with Ctrl+V.

All shortcuts are re-programmable.

It’s that easy. In fact, the only part that might be a bit tricky is if you want to program a site which you want to use and which is not already on Michael’s lists (see below). But there is a “wizard” for that (and the help, of course).

Basic use

You get the installation file on the Version 3 download page (and here is the introduction). During (or after) the installation you can choose to start the program with Windows or put it on the desktop. When it’s activated, a small i is shown to the right in the taskbar, or behind the Show hidden icons arrow. By right-clicking the icon, you open a menu leading to all IWS windows :

And this is the search window, to be opened by Ctrl+Alt+B or the quick menu above:

In the search field on top you will see the search expression, which you can edit. You can also strip numbers or punctuation.

Explanations of the search options (note also the option of using shortcuts here: Alt+underlined figure or letter):

PluriSearch means searching on the sites that you select in a list like this: Click the Search settings button. The Search settings window opens (see figure below). Select the check boxes in front of the sites you want to arrive at (i.e. Group and number) and then use the Add/Remove from list button. Once you’re done, close the window (or go to another one).

GroupSearch means searching in the group that’s open. You select another one using the Group list button. You can rename the group using the Rename button in the Search settings window.

To create a shortcut for direct search on a certain site (instead of using Ctrl+Alt+B), open Search settings, select the site, select Edit > Edit selected, and assign a Shortcut Key. Then click Save and close.

Language combination

Note that for some sites, you need to select a language combination, which you do in the same place where you assign a shortcut, i.e. Search settings. (Select the site, select Edit > Edit selected and make the change in the Finish box – which is usually set to it > en. Example: for IATE

”&valid=Search+&sourceLanguage=it&targetLanguages=en&domain=0&typeOfSearch=t”).

Shortcuts

You set the basic shortcuts (and other stuff) in the Program settings window (which you open via the search window or the right-click menu).

More search sites

For some reason, there are – at www.intelliwebsearch.com/findsearch.asp – some sites which are not on the list in the Search settings window. There you can select a suitable combination of languages and subjects and then download any results – some or all – to your computer. (Select the whole list with Download all as a new user’s starter pack or click a specific site and select Download the settings as a file.) Then add it in the Search settings window (Share > Import from file). Here you will find specialised sites such as IATE Law Domain Term Search, and an advantage with this procedure is that you will automatically get the correct language combination for all sites that you find.

Since I haven’t explored the settings for searching in local term databases, I can’t describe that function. But admit that it sounds exciting!

Good luck!

IATE (Inter-Active Terminology for Europe) is the European Union’s inter-institutional terminology database, and it is such a huge – more than 8 million termpost entries – and comprehensive (and also to a great extent normative) terminology resource that I feel motivated to include some extra information about it.

A good place to start is IATE’s own “Download IATE” page, with a brief description including the number of term posts for each of the 26 languages and a download link.

Further information, including some links to useful sites, is found at the Terminology Coordination site, the Download IATE.TBX page.

If you want to learn about the basics of how to use the gigantic .tbx file and the practical problems associated with that, Paul Filkin’s blog post What a whopper! is a fine place to do that.

If, however, you want to go directly to importing a suitable language pair, then if you’re lucky, Paul has already done the work for you. For 11 English <> [some other EU language], he provides (free of charge) the corresponding .tbx file, as well as for 7 other language combinations involving French, German, Italian, Polish, Dutch, Spanish, and Portuguese. Go to the blog post A few bilingual TBX resources and find out.

However, there are glitches in the IATE base material, and they are present also in Paul’s files. But they have been dealt with in the files that are provided by Henk Sanderson via his SanTrans site (santrans.net). The problems, specified in detail by Henk, are these:

• The handling of synonyms varies.
• Context notes are sometimes inserted in the term itself.
• There are a lot of HTML tags or formatting strings that mess up the term post.
• Subjects are listed as numerical codes which are extremely problematic to interprete.
• Some terms are in fact whole sentences, more appropriate for a TM than for a termbase.
• There are numerous non-UTF-8 characters.
• There are a lot of 1-, 2- and 3-letter words.

Henk has taken care of all this in the files he provides. They are not free, but very inexpensive: 10 euro for the first language pair, 7.50 for each additional pair. Order under the Contact & Comments tab at the SanTrans site. Included are very detailed and easy-to-follow instructions.

You will find all this illustrated in a pedagogical way in Paul Filkin’s blog post IATE, the last word… maybe!.

This will be a long post…

With the cumulative update (CU) 6, on 5 August, the SDL BeGlobal Community was replaced by the SDL Language Cloud. It offers many more options and hence requires a sub-section of its own, which will be included in the upcoming update of the 2014 version of the manual. (Note, however, that this applies only to the 2014 version of Studio. Users of the 2011 and 2009 versions still have access to the BeGlobal Community but not to the Language Cloud.) The SDL Language Cloud gives you the following options:

• Free access to the roughly same facilities as with the BeGlobal Community, only under another name. It is restricted to searching for 600,000 source text characters per month (more than for BeGlobal, where it was 4,000 words per day).
• Basic access, at $10 per month, to 750,000 characters per month (extra characters at $20 per million), plus the option of using one dictionary (i.e. a dictionary for one language combination), where you can upload any number of your own suitable dictionaries. More on that below.
• Advanced access, at $35 per month, to 2 million characters per month (extra characters at $30 per million), plus the option of using 2 dictionaries and 1 specially trained and industry-specific machine translation engine.
• Expert access, at $75 per month, to 3 million characters per month (extra characters at $30 per million), plus the option of using 5 dictionaries and 2 specially trained and industry-specific machine translation engine.

You can try this out for free during 30 days. The trial includes 1 million characters, 3 dictionaries and 3 engines. For those who are familiar with API programming (I’m not), there is also the SDL Language Cloud Translation Toolkit (at https://langu­agecloud.sdl.com/translation-toolkit/api-documentation), which enables devel­opers to submit content for translation via the SDL Language Cloud translation platform.

Getting started

If you don’t have a Language Cloud account when you open Studio, you will be greeted with a Welcome to Language Cloud window. Click Next, log in, and then click Finish. This establishes your account with Language Cloud, and the 30 day free trial will be activated at the same time. Next, go to File > Language Cloud. The LC account summary will open in the right-hand pane, detailing the details of the trial option:

When the trial period is over, you will be requested to select a subscription option.

The SDL Language Cloud page

All manipulations of your Language Cloud account is done on the SDL Language Cloud page, which you reach via Studio: Go to File > Langu­age Cloud, then select the Manage Subscription button (or, as the case may be, the Upgrade your subscription button). You will be taken to your account page, showing your Current packages:

– Plans and pricing: If you want to see the different options (or select one of them), select the Pricing tab:

– Available languages: On this page there is also a link to a list of all available languages (you can find it direcly – without being logged in – at https://languagecloud.sdl.com/translation-toolkit/available-machine-translation-language-pairs).

– Customized package: If In addition, you can have a subscription package taylored to your specific needs: scroll down to the Need more? part:

As for the other tabs – Overview, API Documentation, and FAQ – I leave them for you to investigate.

Dictionaries

A dictionary in the Lanugage Cloud is an empty container specifying source and target languages, and you then fill with content of your own. The difference between having those entries automatically looked up in a MultiTerm termbase and in a Language Cloud dictionary is that in the former case you will see the hit in an AutoSuggest list – and have to select it manually if you want to use it – whereas in the latter case it will be automatically inserted into the machine translated target segment.

– Add a dictionary: On the SDL Language Cloud page, go to the left-hand menu and select Translation Tools, then Dictionaries. The Diction­aries pane opens. If you haven’t created any dictionaries, you’re invited to do so. Otherwise, the pane looks like this:

Click the New Dictionary button. The Add a New Dictionary pane opens:

Fill in the fields and select languages, then Save. Now you can import content, or you can do it later. The Dictionaries pane will list the new dictionary (dictionaries).

– Import dictionary content: You can, at any time, import new content into your dictionaries. Go to the Dictionaries pane as described above. Click the Edit pen for the dictionary in question:

The Manage Dictionary pane opens:

Click the Import button and upload your dictionary file (must have a TBX or XML file extension, TBX being the XML-based standard for exchanging terminological data). Note that neither the Studio SDLTB nor the old MTW will not do, so you may need to open the dictionary in MultiTerm and export it to the appropriate format. (In the Upload file box which opens when you click Import, there is a link – Learn more – to Knowledge base entry #5267 with a video showing the full import process including how to export from MultiTerm.)

Note: To get the best results you should simply your termbase, making it one-to-one (synonyms are not handled intelligently in Language Cloud dictionaries). This dictionary function is at its best when you are using very specific terminologies, such as for brand guides.

In the same Manage Dictionary pane, your imports – successful and failed – will be listed in an Import History list.

– Search for dictionaries: On top of the Dictionaries pane (see above) there is a search field. It is used for searching for a particular dictionary. Why would you do that when even the Expert subscription only gives you 5 dictionaries? The answer is found further down on the pricing page: “Need more? Contact us to discuss packages and pricing.” If your needs are such that you handle 30 different dictionaries (or millions of words per day), there is a solution for that, too. And then the search function (plus the box for specifying how many hits per page you want) may come in handy.

Engines

An Engine is a more or less specialised application of machine translation. The one which is included in the free option is the same as before, in BeGlobal Community, which means a  general content TM for automatic translation much like Google Translate or Bing. For the paid options, there are specialised engines – currently, however, only with English as source. This is because so far, these are the only ones “trained” enough to give demonstrably better results than the standard ones. (I haven’t checked this myself.) The domains of specialisation are Automotive, Electronics, IT, Life Science, and Travel (not all of them are available for every language combination).

(The training of an engine – possible if you use BeGlobal Enterprise – requires statistically significant volumes of translation data, preferably more than half a million words per update. For an organisation doing a lot of translation this may be a worthwhile exercise, but it is hardly useful for the freelance translator.)

– Select engines: On the SDL Language Cloud page, go to the left-hand menu and select Translation Tools > Engines. Then click the engine(s) you need. Once you have saved your selections, you cannot change them until the next billing period – see below.

Billing period

To see your current billing period: On the SDL Language Cloud page, go to the left-hand menu and select Subscription. You can change between Auto-Renewal and manual renewal anytime you want. Just click the left-hand or right-hand part of the Auto-Renewal part here:

In this example, the Auto-Renewal option is on, and the wording “Active until” means that the subscription will be automatically renewed on the specified date. If the Auto-Renewal option is off, the corresponding wording will be “Expires on” (which is a lot more clear than “Active until”, I would say).

Current subscription status

You can always see the current status of your subscription (package type, how much you have used, etc.) on the Summary pane which opens when you select, in Studio, File > Language Cloud.

Menu items

The left-hand menu of the SDL Language Cloud page gives access to resources as follows:

Summary: The summary of your current subscription activities (see above) which is also shown in the Studio window via File > Translation Cloud.

Subscription: The Current Package / Available Packages pane (see above).

Translation Tools: Sub-items Dictionaries and Engines (see above).

Integrations: Sub-item API Keys; for the creation of API keys (for more information, select the API Documentation tab).

Analytics: Sub-items Machine Translation and Human Trans­lation; for reports on your usage of those features.

Profile: Sub-items User Information, Account Information, and Password.

Administration: Sub-items Account Balance, Billing Details, and Translation Limits.

Important!

Make sure to read Paul Filkin’s multifarious posting on this topic – particularly if you’re a 2011 user who has run into an error message telling you that you have exceeded the maximum number of words per day, even though you know you haven’t.

It’s not uncommon that the Update from External Review ends in error. This will happen if the review document was handled in Word 2003 or previous versions (even if the .docx format is retained), but it can happen for other reasons as well. However, this is often a solution:

1. Open the problematic reviewed document in any version of Word and accept the changes as desired (if you haven’t already).
2. Copy the thus changed reviewed target column.
3. Insert the copy into the original review document and, as applicable, delete the extra right-hand column or accept all changes.
4. Save the amended original review document and use that for the update process as above.

It has happened that a user opens Studio and, inexplicably, the interface language is Chinese! What to do when of course you cannot understand any of the commands? Here is how: click the highlighed button as shown below:

Then, in the new dialog box (below), click the downward arrow and select your language.

Click the OK button (which is in its usual place: second from the right). That’s all!

The OpenExchange concept is a brilliant idea, but navigating the OpenExchange site is a bit unwieldy. Hence my table at the Manual site, which presents all plugins/applications all at once; you can also sort them by clicking on the column headers. Links give direct access to the respective OpenExchange presentation page as well as to the respective developer.

Click on the header above (OpenExchange Overview) or here.

I don’t like reading long texts on screen. Also, I often need (or think I need) to save interesting and/or important stuff on paper.

But screen content is often cluttered with all sorts of irrelevant material. And sometimes also the layout makes direct printouts difficult to handle and read (e.g. the type size may be inordinately small on paper). One method to obtain nice printouts is to copy the relevant content and paste it into Word, whereupon you can edit it as you like. But this is not always easy; some web pages are very difficult to edit even in Word format.

However, there is a solution. At the click of a button, the Evernote Clearly application (http://evernote.com/clearly/) reformats the web page content to something which looks good on paper. ProZ discussions is a good example. This is how a discussion looks originally on-screen:

On several occasions, I have copied and pasted ProZ content into Word, but the convoluted table format makes it very difficult to achieve a good printout even so. With Evernote Clearly, this is what you see in your browser:

Obviously, this makes for a good printout. If you copy it into Word, the table layout is still there, but it’s relatively easy to re-format it as you like it.

Evernote Clearly is free and very easy to install and use. Its one drawback is that it only works with Google Chrome. It seems to work as expected on almost all occasions; only once did it happen that the selected content was not what I wanted. Good stuff!

If you have the automatic update function activated (it is by default: check under File > Options and Automatic Updates in the left-hand pane), you would have been prompted to update a few days ago (or anytime after that if you bought Studio later). This would have given you the Cumulative Update 2, or CU2. So what does that mean? All the details are here: http://kb.sdl.com/kb/?articleId=4947#tab:homeTab:crumb:7:artId:4947

but mainly it means that you can now update your Java plugin without risking problems in Studio (providing you use the 32-bit Java version). It also means “major enhancements to the new SDL Trados Studio Integration API”, which in turn means – I hope – that even more people will provide OpenExchange applications (for which we are always grateful).

One other notable improvement: “intermittent issues with legacy termbases requiring reorganization no longer occur”. Good to know.

This is a function for inserting placeables/tags in the target text that I have come to appreciate very much: By pressing Ctrl+Alt+RightArrow/LeftArrow, you step between the placeables/tags in the source element, forwards or backwards; each placeable/tag is highlighted in turn. When you come to the correct one, you just press Enter to insert it. In a segment with many placeables/tags, this is really useful.

However, suddenly what happened when I used that command was that instead of the expected result, the screen was briefly blackened and then, when it showed again, it was rotated! Totally bizarre and not useful at all.

The problem, it appeared, was to do with the Intel Video programming, which had been reset following an update of its driver. The solution was to inactivate the Intel Video shortcuts: right-click the screen, select Graphics Options > Shortcuts > Inactivate.

Probably a seldom occurring issue, but it may be good to know what to do if you happen to be affected.

Sometimes you have a Word document with source and target texts not in the usual Trados bilinugal format but simply as two columns in a table. Roger Sjölander’s nice macro handily transforms that table into a TM file in text format (but first make sure that the source is in the left-hand column). The macro is called Modul 1.bas, and you will find it here.

As with all .bas documents, you open the MS Visual Basic window (Alt + F11), open File > Import file and import the file in question.

If you want to assign a shortcut to it, here’s how (in case you do not remember):

Open Word’s Tools > Customize dialog. Click the Keyboard button. In the Categories list, click Macros. Select the macro in the list to the right. Enter the shortcut in the Press new shortcut key box, then click Assign then Close and Close again.

If you don’t use shortcuts, here’s how to run the macro:

Open the macro window (Alt + F8), go to the macro and click the Run button.

PS. If you receive a “5156 runtime error” message when you use the macro, it may be that you are trying to save the resulting file directly in the root catalogue (usually C:). Try moving it to a subdirectory (existing or new).