1. Lucas Tissier,
Digital Marketing Assistant, SDL
Ask the Experts: SDL Trados live Q+A webinar
for freelance translators
Paul Filkin,
Client Services Director, SDL

2. The Freelance Translator’s
Road to Success:
info.sdl.com/road-to-success

3. V1.5
Ask the Experts:
SDL Trados Q+A
webinar for freelance
translators
Paul Filkin

4. 01 – Getting Help
02 – Licensing & Installation
03 – Working with Projects
04 – Working with Packages
05 – Sharing Work
06 – Working in the Editor
07 – Working with Translation Memories
08 – Upgrading Resources
09 – Working with Filetypes
10 – Machine Translation
11 – Productivity & Helpful Tools
12 – SDL MultiTerm
Agenda

5. 1. I'd like to learn about SDL Trados generally since I know it and want to use but I'm
not familiar at all yet.
2. How to get started using Trados
3. Is it necessary to upgrade Trados to the most recent version every year?
4. What do you get with a support contract?
5. What to do when there is a pop up that says: object reference not set to an instance
of an object?.
01 Getting help

6. YouTube - youtube.com/user/sdltrados
• ‘How to’ videos for
Studio 2019 and other
versions
• Information on new
features and releases
• Getting Started videos
• SDL AppStore app
demonstrations

7. SDL Customer Gateway
https://gateway.sdl.com/
• Access Knowledge Base
• Library of product documentation
and technical solutions
• Access to Community

8. SDL Community
• Access via http://xl8.one – using same sign-on as your SDL Account
• Managed by SDL product experts, industry professionals and your colleagues
• Any question - technical issues or how to use Studio, MultiTerm and SDL Language
Cloud and SDL Apps

9. • Supported by the Customer Experience
Team (sdl.com/livechat)
• ‘How to’ help for ‘new to CAT tool’ users
• Quick technical solutions for existing users
• Support with installation and licensing issues
• Help and information on how to upgrade
• Available 9am – 11pm CET - Monday to
Friday
SDL Customer Experience Live Chat

10. Support and Maintenance in a nutshell!
Formal support … this means:
• Limiting downtime
• Unlimited support requests
• Live chats for License resets
• 1 hour critical case maximum response time
• Known fixed costs for your annual business budget
• 3-month option for Freelancers
And Maintenance means:
…. FREE upgrades to the next version

11. SMA – THE
DETAIL

12. To request a quote login to your SDL Account then fill in the short quote form OR
Contact our customer care team by telephone or email: contractrenewals@SDL.com +44 1628 410 165
Response times: Hours support available:
*
*Maintenance is not included with the 3-month contract

13. Support and Maintenance options
(€50 – current 17 June 2019)
Now available for all options :
• Choice of support region - providing support in the hours you need it most

14. ERROR
HANDLING

15. The first thing to note…
• If you check this option every
error, whether you see it or not
will be fed back automatically to
the development team.
• This allows them to work on fixes
and add them to future updates
making the software more
reliable and more performant for
everyone.

16. When you see something like this for any Studio or
MultiTerm error click on the small disk symbol and
save the xml error file to your desktop.
Attach this file to your post in the community or to a
support ticket
• Provides information a developer can use to resolve the
problem (screenshot isn’t helpful)
• Take a look yourself, sometimes an educated guess will
help you solve the issue so you can carry on working…
In this case removing the Beta version of the Studio
Subtitling plugin I was testing resolved the issue.
… in the meantime

17. The most common solutions… 1 of 2
To troubleshoot files try this article (How to troubleshoot problematic files)
https://gateway.sdl.com/apex/communityknowledge?articleName=How-to-troubleshoot-
problematic-files
More often, the solution to these problems is resolved like this:
• Open the source file again using the "Translate Single Document" process
• Save it to create a single file project
• Try to save target now before you do anything. If it works go onto the next step, but if it
doesn't then you need to consider the more advanced trouble shooting steps in the KB
article as it may be a problem with the source file
• Pretranslate the file using your Translation Memory
• Save the target file

18. Use this app from the SDL AppStore to carry out a controlled reset. The app will also explain what you may
lose by carrying out a reset before you do it:
https://appstore.sdl.com/language/app/sdl-freshstart/876/
Or do a full reset manually… rename this folder (just add _old to the end or something, it's not important what
you rename it to) and restart Studio:
c:Users[USERNAME]AppDataRoamingSDLSDL Trados Studio15.0.0.0
So the path would become this:
c:Users[USERNAME]AppDataRoamingSDLSDL Trados Studio15.0.0.0_old
If you can't find this folder then you need to unhide your hidden files/folders:
https://www.howtogeek.com/howto/windows-vista/show-hidden-files-and-folders-in-windows-vista/
The most common solutions… 2 of 2

19. 1. I reinstalled SDL Studio 2017, but every time I turn PC on, a new installation window
opens requesting installation. Besides, my previous installation is working well.
Would you happen to know what the issue is?
2. Can I use my license on multiple devices / IP addresses at the same time?
3. I have 5 preset languages in SDL Trados for freelancer. Now I need to replace 1 of
the 5 with another one. How can I do it?
02 Licensing & Installation

20. If you’re completely stuck…
First of all note we have an excellent series of wiki articles here:
https://community.sdl.com/product-groups/translationproductivity/w/customer-experience
Then for licensing or installation issues that prevent you from working we also have a route for all customers
to get help. This can be achieved really quickly using this link:
https://gateway.sdl.com/liveagentlicensing
You have two options:
1. Submit a case using a webform
2. Use live chat to get a licence reset
If you have a support contract then you don’t need this and you should log in through the SDL Gateway and
submit your request there.

21. Licence types…
Express Single user • 1 activation at a time, renewed annually, locked to a
specific TMS
Starter Single user • 1 activation at a time, renewed annually
• Cannot be run on a domain network
Freelance Single user • Perpetual licence, 1 activation at a time, unless you have
Freelance Plus and then you have 2.
• Cannot be run on a domain network
Workgroup Single user
Network licence
• 1 activation at a time
• Network licence means as many concurrent users as
were purchased
Professional Single user
Network licence
• 1 activation at a time
• Network licence means as many concurrent users as
were purchased

22. Changing one or more of
the five selected languages…
Prior to Trados Studio 2019 SR1 and 2017 SR1 CU15 changing the languages could be achieved
by running a repair installation through the windows control panel, or by carrying out a reset
(mentioned in an earlier slide).
Unfortunately this is not possible anymore so the safest solution is to contact the Support Team
using https://gateway.sdl.com/liveagentlicensing and they will do this for you.
For the brave of heart, there is a registry edit that will reset the languages and for this I
recommend you visit the SDL Community and type “reset freelance languages” into the search.
You will find this forum post with all the instructions you need:

23. 1. Sometimes when I create a project to translate, with more than one file, as I open
the first file to work on, the memories selected do not appear. It drives me crazy...
2. I m translating German and English Text into Urdu (my National Language and my
mother Tongue) and Vice Versa. How much support do I get, if I use SDL Trados to
execute my project as far as creating a termbase and translation matching of
previous and existing translations is concerned.
3. In my TM file there is one "AnyTM" set by default. How can I avoid that situation?
4. Do you have to update the individual project memory and the overall memory in
any way?
5. I have several translators, is there a review functionality/ to manage the workflow?
Can translation memory be updated?
03 Working with Projects

24. When you work with a Studio
Project you can use “Project
Templates”. These control
which resources and languages
will be used.
You can edit the templates in
File-> Setup -> Project Templates
Project templates… 1 of 2

25. Project templates… 2 of 2
I added this slide in later as I was asked a question about applying project templates to
packages or projects received from others. This is so you can add your own TMs,
AutoSuggest Dictionaries, QA rules, Terminology etc.
This is all possible using an application called Apply Project Template from the SDL
AppStore. This article is specifically about this topic and perhaps worth a read:
https://multifarious.filkin.com/2015/06/02/keep-calm/

26. A possible reason for a missing TM…
• If you set up a template with multiple variants of a target language only the
relevant TM will be available for use, so in this example only en(GB):
• Open the fr(FR) – en(US) or en(CA) files and you’ll see this:

27. Multiple source languages…
• If you speak multiple source languages into one target language you could use
project templates to help:
• You’d need separate translation memories, so
en-ur.sdltm in one template, and de-ur.sdltm in
another…
• But you could have one multilingual termbase used
in each:

28. Resources set up by default…
• If you use templates you can use a resource such as AnyTM and this does allow
you to resolve the problem we just saw:
Now this single TM will be used irrespective of the language pair
• But if you have AnyTM appearing by default and you don’t want it then remove it
from your template. A “problem” designed to help is that when you add a
resource during project creation it will become a permanent part of your default
template.

29. Project memories and Main memories… 1 of 2
• When you create a project you have the option to “Prepare without project TM”
or just “Prepare”. The default is “Prepare without project TM”
• If you use a project TM it’s indented below the Main TM with the project name
appended to it:

30. • The project TM is populated from the Main TM when you create your project and
based on matches above the minimum defined here in your project template
settings:
• This allows you to share a small subset of your Main TM with content that is likely
to be relevant.
• When you translate you will be updating your project TM and not your Main TM.
You only update your Main TM at the end, either by running a batch task to
“Update Main Translation Memories” or by running the “Finalize” task.
Project memories and Main memories… 2 of 2

31. Review functionality…
• Trados Studio has a simple 3-
stage workflow that is available
for use:
1. Open for Translation
2. Open for Review
3. Open for Sign-off
• To use just open the file for use
in one of these modes.
• Translations are confirmed in
each stage as follows:
• Each stage can have
different statuses to
help you track progress
through the workflow

32. 1. How to open a Return Package if I am not the one who create the initial package?
2. Is it possible to edit a return package before re-creating an ultimate return package
to send to the client?
3. How to prevent sending personal translation memories and termbases back to the
customer? For example, when creating a return package?
04 Working with Packages

33. A few things about Return Packages…
1. Packages are essentially zip files with a different
extension.
• sdlppx – project package
• sdlrpx – return package
2. If you receive a return package that doesn’t relate to a
project package you created you can unzip it and take
the bilingual files out
3. This means you could, carefully, make corrections in
the sdlxliff files by handling them in your own project
and then put them back into the zipped sdlrpx
afterwards
4. Return packages only contain the bilingual files…
there is no mechanism for your termbases or TMs to
be in them. But don’t just trust me… unzip one and
take a look for yourself!
5. You can also use the Package Reader from the SDL
AppStore to quickly review the contents of a package

34. 1. Is there an easy way to share a project on two different computers? For now it
seems i must export the project and also the TM separately.
2. I have Freelance edition and need an efficient process to send projects to my
colleague for proofreading and working on same files. Packages are not possible. We
are currently trying the Dropbox solution, but it is quite slow and we could use some
do's and don'ts with this work-around.
3. Is it possible to save translations (source and target text) not made with Trados
Studio in Trados Studio?
05 Sharing work

35. Sharing work… 1 of 3
• Potentially a bigger topic than I can squeeze into here so I’ll refer you to this article:
https://multifarious.filkin.com/2014/12/08/with-a-little-help/
• You can share sdlxliff files
• Translate in your project
• Send to your colleague as sdlxliff files from the target language folder of your project
• No need to do anything special, just close the files so they are not open and the
sdlxliff files in that folder are ready to go
• Open for review perhaps so you change the segment statuses to track progress
• Send back when you are done
• Backup the original sdlxliff files in the target folder (zip them, or rename them)
• Copy the reviewed sdlxliff files into the same folder
• Open the project and you’re good to go
• You can export QA profiles if needed and share them

36. • If you need to share TMs or Termbases it makes sense to use something like dropbox. But
you can improve the experience a little by not trying to read/write to the same resource.
• Termbases can be tricky if you mess the index files but TMs are relatively simple. Imagine
three colleagues working on a shared project, all with the same Project TM.
• Create three copies at the start
• Then set up your respective projects like this:
• Each one writes to their own and
reads the others
Sharing work… 2 of 3

37. • Working with bilingual files created by other CAT tools
• Depending on the tool Trados Studio can support it
• xliff, mqxliff, mxliff, txml for example
• ttx, bilingualDOC… of course
• Can save the target file from a ttx or a bilingual doc
• Cannot save the target file from the bilingual format created in any other tool. Can
only save what went in… for example:
Sharing work… 3 of 3
mqxliff sdlxliff mqxliffdocx docx
txml sdlxliff txmlxlsx xlsx
xml sdlxliff xml

38. 1. How can I zoom in to make ALL of the text on the screen larger?
2. Can you correct a source segment?
3. If you have a sentence that has been split in two lines in your source document, how
can you merge it together so that the translation is on the same line or entry?
4. How do you add the tags in the right places in the target segment if the source
segment includes multiples tags?
06 Working in the Editor

39. Zooming text… 1 of 3
Editor
• To set a default size – File -> Options -> Editor -> Font Adaptation
• To change it on the fly

40. TM Results, Concordance, Fragment Matching
• To set a default size – File -> Options -> Translation Results Window
• All three have these options:
Term Recognition
• In theory you can change the size of the text in the Term Recognition window “Hitlist
settings”. In practice it’s very sensitive and not responsive… so care should be taken:
Zooming text… 2 of 3
File -> Options -> Fragment Matches Window
File -> Options -> Concordance Search Window

41. Translation Memories View
• To set a default size – File -> Options -> Translation Memories View
Zooming text… 3 of 3

42. Editing source…
• To edit the source using the Studio Editor you need to make sure that “Allow source
editing” is checked in your Project Settings:
• If you want to make wide ranging changes to the source you can use an app called
the SDLXLIFF Toolkit which will allow you to use search & replace operations on the
source or target text of all the files in your project.

43. • You can select multiple segments that don’t
cross paragraph boundaries and merge them
with a merge command
• If they do cross paragraph boundaries you
can enable this too, but be aware of the
implications:
Merging segments… 1 of 2

44. Merging segments… 2 of 2
• This is what could happen if you merge where you should not, or if you try to
override a restriction the project manager applied to the project to prevent merging
across paragraph boundaries:
• This article may be worth a read for more details on this topic:
https://multifarious.filkin.com/2016/11/21/bridging-the-divide-merging-segments/

45. Handling tags…
• Referring to this article for a full explanation of all the options around tag handling in
Trados Studio:
https://multifarious.filkin.com/2012/09/10/working_with_tags/
• Important to note
• Always place the tags from the source into the target
• Only use the Bold, Italic, Underline to introduce formatting that wasn’t there in
the first place
• Other useful things to remember:
• File -> Options -> Editor -> Formatting Display Style to change defaults for tag
display
• Ctrl+Alt+D – toggles tag formatting
• Ctrtl+Shift+H – turns on or off the display of formatting tags
• Ctrl+comma – places the next opening tag or a placeholder tag
• Ctrl+fullstop – closes an open tag

46. 1. When I merge multiple documents this app records the name of the first document, not the
document with the actual TU. I word with many fields and it is very important for me to
know exactly from which document the TU comes from. Thus, this behaviour is not helpful.
I saw in the community that someone else had a similar problem. Is this a bug and will it be
fixed soon?
2. If you make changes to a 100% match or CM, are you creating a new entry on your TM or
are you just modifying?
3. I've created a TM for each of my customers (different specialties). Is that ok?
4. What does the plus sign mean next to the match percentage in the Translation Results
window?
5. If I have a model source text, and its translated version. Is it possible to add it to the
Translation Memory? if I know I have a similar document to translate
07 Working with Translation Memories

47. RecordSourceTU…
• Excellent little application that automatically stamps the TUs as you work with
one, or all, of the following:
• If you merge the files for translation it’s not working correctly… we’ll fix that asap!

48. Interpreting TM Results… 1 of 2
• Different source, same target:
• Same source, different target:
• You can change this penalty, and more, in the settings:

49. Interpreting TM Results… 2 of 2
• When working interactively, if you change a 100% or a CM match you will overwrite the
TU that is there… with obvious exceptions:
• If the 100% comes from a different file in a different context then Studio will add a
new TU but always present the correct one in the correct context
• If you use “Add as new translation”
• When working with pre-translate you
can control the behaviour with options:

50. Big mama or multiple TMs…
• This question comes up a lot… should I have one big TM or lot’s of small ones
separated by speciality or by customer for example. What’s the best practice?
• The answer is… there is no best practice. Trados Studio is flexible to suit your needs.
• You can use multiple TMs in a single project so you don’t need to have one large
TM
• If you have one large TM you can use Fields and Attributes to separate the
translations for easier maintenance… but it takes careful planning and diligent
use
• Both methods work… it’s entirely up to you. Separate TMs are probably easier to
manage if you only have a few. If you really do need to separate the content into
many different types then one, or a few TMs with Fields and Attributes might be
better. Perhaps review this article for more information on this:
https://multifarious.filkin.com/2013/07/12/fields_attributes/
• Don’t forget you can use Project TMs to make it easy to provide a TM for a specific
job, or even import the sdlxliff files into a new TM

51. Alignment…
Source and target files can be aligned
and added to a TM
The new version of Alignment in
Trados Studio 2019 offers a huge
improvement over previous
incarnations.

52. 1. I use SDLX 2016 Build 6010 and have a couple of huge EN-SPmodern TMs; If I buy
SDL 2019, is it possible to migrate these 2 TMs or change it to just EN-SP without
issues?
2. Is there an easy way to merge 2 or more translation memories that you have
created?
3. I am using MemoQ at the moment. Can I convert that TM to be used in Trados? TM
is my great asset so I would like to keep on using them.
08 Upgrading Resources

53. Merging TMs… 1 of 2
• Note: Translation memory upgrade can be performed in batch mode with multiple formats and language pairs
processed
– The upgrade process will create new 2019 translation
memories, *.sdltm
– Existing files will not be deleted when upgrade is
complete

54. Merging TMs… 1 of 2

55. Merging TMs… 1 of 2

56. Merging TMs… 1 of 2

57. Merging TMs… 1 of 2

58. Merging TMs… 1 of 2

59. Merging TMs… 2 of 2
Primarily with new, native source files or files processed only with SDL Trados Studio
“Clean up” the imported Translation Units
Closer to what the new filters are likely to produce

60. Primarily with presegmented legacy SDL Trados ITD or TTX files
Better to leave the TM contents unchanged during migration/import, or only minimally changed
• Fix obvious mistakes in the legacy filters
• Adjust for special/changed behavior of the new ITD/TTX filters
• Most cleanup heuristics affect the tags and how they are represented
Merging TMs… 2 of 2

61. Merging TMs… 2 of 2
Primarily with new, native source files or files processed only with SDL Trados Studio
“Clean up” the imported Translation Units
Closer to what the new filters are likely to produce

62. Using TMs from other CAT tools…
• The way to go here is TMX. All CAT tools that I am aware of are able to support an export
to TMX.
• Once you have the TMX you can do one of two things:
• Upgrade it as previously shown
• Import it into an existing, or new SDLTM
• For memoQ specifically as this was the question….

63. 1. Why is it that some files do not open well on SDL Trados?
2. Can I read/open all kind of pdf's into Trados Studio?
3. How does a .pdf file have to be in order to convert it properly? ...I got some
problems with them. Are there some settings in SDL for adjusting the .pdf file before
convert it in SDL?
4. When trying to verify XML files, I constantly get the message "No schema for the
verification found". Why is this and is there any way out?
5. How can I deal with text Codifications? Does the new Trados include a tool to check
and change this in an easy way? For example, from ASCII to UTF-8
09 Working with Filetypes

64. Working with PDF files… 1 of 2
• PDF, Portable Document Format, should always be the last resort as a filetype for translation. The quality
varies depending on how it was created:
• It wasn’t necessarily created from the original source so the text quality and consistency can vary
• Could contain translatable text… could be an image of the text
• Could contain a lot of formatting which makes the conversion and rendition into Word quite tricky
• … etc
• Sensible pre-requisite for handling in Studio
• Install IRIS from the appstore
• Make sure it’s activated under File -> Options -> Filetypes -> PDF

65. • The process from then depends on the quality of the PDF
• If the quality is awful you may be better off recreating the source file in a suitable DTP software
• If the quality is not bad, but contains too many tags, unnecessary line breaks etc then do the
following:
• Open as a single file translation in Studio
• Immediately close the file after it’s opened for translation
• Look in the same folder as the PDF and you’ll find a DOCX
• Clean up the DOCX using Word, or maybe a tool such as TransTools (also on the SDL AppStore)
• Translate the cleaned up Word file instead
Working with PDF files… 2 of 2
• If the quality looks good just go ahead and translate in Studio
directly from the PDF. The target file will be a DOCX and not a
PDF so if you need to deliver a PDF you simply save the DOCX as
PDF when you have finished the job
• There are other tools such as AbbyFineReader, or InFix for example.
But often the process above will be enough and won’t cost you any
additional money. If you do a lot of PDF translation however then it
would be worth investigating a professional approach using more
sophisticated tools

66. Working with XML files… 1 of 2
• If you constantly get the message "No schema for the verification found“ and it’s not
important for you to know this then simply turn off the verification in the filetype
options. The default is this:

67. Working with XML files… 2 of 2
• Encoding is a fairly common issue and it helps to understand a little about this. Perhaps
worth reading this article as it refers to encoding issues general as well as within Studio:
https://multifarious.filkin.com/2015/12/01/encoding/
• Also note this application from the SDL AppStore that is incredibly useful for dealing
with encoding problems and allows you to batch convert the encoding in any number of
files as well as being smart enough to identify where the problems probably lie so you
know what to fix:

68. 1. Could you provide a demonstration of how to optimize using the Deepl plug-in with
SDL Trados?
2. If I use several AT resources, e.g. DeepL as well as SDL Language Cloud, can I change
the AT tag to show which resource was used?
3. How do I not show I received AT as the source of my translation?
4. Does the cloud translation resource imply confidentiality issues regarding disclosure
of our contents?
10 Machine Translation

69. Working with MT providers…
• When you use MT you have several ways to work with it:
• Pre-translate and Post-Edit – will ensure AT status:
• Interactively with or without Autosuggest – will avoid AT status:

70. Traceability…
• When you use MT every segment receives an AT status which holds the value of the MT
provider that was used. This is important information for a project manager who is
supporting the use of multiple engines and needs to be able to check which one was
used:
• The provider used when the translation is complete is displayed and also the
provider that was used in the first place:
• The tag itself cannot be changed to reflect which provider was used

71. Removing traces…
• If it’s not important to retain this information it’s simple to
remove the AT status using the SDLXLIFF Anonymizer app from
the SDL AppStore:
• You can also remove it doing the following:
• Confirm all AT segments to a TM
• Clear all these segments
• Pretranslate from the TM
• Use a penalty on the TM if you don’t want 100%
matches in there
• Or of course work with AutoSuggest or copy paste from the TM
results window

72. Confidentiality…
• If you use MT you have to send the source to a provider. If you use Google or anyone
else for example then you are at risk based on what Google or anyone else does with
that data
• If you use SDL Language Cloud the details are here:
https://www.sdl.com/about/privacy/sdl-language-cloud-privacy-policy.html
How SDL plc may use the source material
• To provide the services ordered: SDL represents that during the machine translation process none of
the source material will be needed, stored or used in SDL's translation engines, except for term
dictionaries, which will be stored securely.
Security
• SDL will take reasonable efforts to safeguard your information from unauthorized access.
• Source material will not be disclosed to third parties. Your term dictionaries are for your personal
use only and are not shared with other users using SDL Language Cloud.

73. 1. How to improve productivity and speed up processes with Studio 2019 and the best
apps to work with Studio 2019.
2. How did you get the community filter to appear in trados. I have now installed it but
dont know how to activate it in a project
3. Checking tools? ie. grammar checker and maybe Synonym drop-down in Studio
Editor
11 Productivity and helpful tools

74. Where do plugins get installed… 1 of 2
• When you download an sdlplugin from the SDL
AppStore you save it to your desktop (or a folder
of your choice) and doubleclick it. This will take
you through the plugin installer wizard and
install the plugin into the appropriate folders for
your version of Studio:
• In this example I’m installing a plugin that has
been designed for the 2019 version only so all
other versions of Trados Studio I have installed
are ignored

75. • As part of the wizard you are asked where you would like to install the plugin. For the most
part you should accept the default:
• But if you have a specific requirement you can use other options… this is what they mean:
• All your domain machines – used if you login to another computer in the same domain
network. Means you can run Trados Studio if it’s installed and access your own plugins
• Local machines – used if you have multiple users accessing the same computer and
running Trados Studio but they all work with their own preferred plugins. Plugins
installed here will not be available to you if you log into another computer on the same
domain network
• Program data – used if you have multiple users accessing the same computer and
running Trados Studio and they all need access to the same shared plugins
Where do plugins get installed… 2 of 2

76. Once installed where do they appear… 1 of 3
• This entirely depends on the plugin and what it does. The Community Advanced Display
plugin and many others that add new views into the product are often found under the
View menu like this:
• Plugins that add Machine Translation providers or Terminology providers would be
found when you add a TM provider or a termbase, like this:

77. Once installed where do they appear… 2 of 3
• The plugin might add a batch task to Studio and then you would find it here:
• It could even be a new QA check of some sort:

78. Once installed where do they appear… 3 of 3
• Some plugins are so extensive they are essentially a new application all of their own:

79. Checking Tools…
• We’re essentially talking about QA plugins, so here’s a list of what’s available on the SDL
AppStore:
• Antidote verifier: https://appstore.sdl.com/language/app/antidote-verifier/583/
• Language Tool – Grammar and Spell Checker:
https://appstore.sdl.com/language/app/languagetool-grammar-and-spell-checker/725/
• MS Word Grammar Checker: https://appstore.sdl.com/language/app/msword-grammar-
checker/392/
• I put this here but would recommend not using it with new versions of Word. It will not work and we
can’t resolve it because Microsoft have removed all means we had of ‘hooking’ into it. There has never
been an API available for this from Microsoft
• Acrolinx for Passolo: https://appstore.sdl.com/language/app/acrolinx-for-sdl-passolo/325/
• SDL Number Verifier: https://appstore.sdl.com/language/app/sdl-number-verifier/440/
• ApSIC Xbench Plugin: https://appstore.sdl.com/language/app/apsic-xbench-plugin/354/
• Xbench 2.9 Plugin: https://appstore.sdl.com/language/app/xbench-2-9-plugin/729/
• Verifika: https://appstore.sdl.com/language/app/verifika-plugin/432/
• Take a look and give them a try!

80. 1. Why am I not able to insert accents on letters in Multiterm base?
2. Can you have multiple termbases open at the same time when translating a
document?
3. What's the difference between add new term and quick add new term?
4. Can we convert our XLS or DOC Glossary into SDL Termbase? If yes, how?
5. Do you create one termbase for each of your customers in different fields?
6. What happens in Glossary Converter if there are two translations for term?
12 SDL MultiTerm

81. Working with MultiTerm… 1 of 2
• Using diacritics on letters in Multiterm… it should just work:
• We probably need more information on why this isn’t possible…
I’d recommend http://xl8.one
• Working with multiple termbases… you can have as many as you like, and you can mix
providers

82. Working with MultiTerm… 2 of 2
• If you do work with multiple providers there are a couple of things to note:
• One of them will be the default. You decide which one that is.
• Only the default can have terms added to it. Unfortunately there is no way to add
terms to a different termbase in your list unless you use something like autohotkey
and run a script to allow you to change the default and add terms to the termbase
of your choice
• Only the default will use the preview pane
• The difference between Add New Term and Quick Add New Term is not noticeable if
you use the default view as the behaviour is actually the same. But if you use a different
layout, such as the Flags Layout below then Add New Term opens the editor and allows
you to edit the entry and then click to save it.
This is very useful if you are working with an
extensive layout containing many different fields
that need to be populated as you work. Quick
Add New Term adds the term instantly with no
ability to edit:

83. A feature of the Glossary Converter…
• If you need to convert a glossary from an XLS or DOC file then the Glossary Converter
makes short work of it! It’s a simple drag and drop best explained with these resourses
rather than pictures in a slide:
• For a short and very happy demonstration - https://youtu.be/Ypirl8P26_E
• For a longer and more complex example - https://youtu.be/w5DaMDH8AlI
• For more information on the Glossary Converter in general as it can do a lot more than
simply work with glossaries:
https://multifarious.filkin.com/2015/12/09/feature-rich/
• To answer the question about synonyms. You ensure that you have one glossary entry
per row and then separate synonyms with a recognised character… the default is a pipe
symbol:

84. And finally…
• “Do you create one termbase for each of your customers in different fields?”
This is entirely up to you! You can use Fields and Attributes on a termbase to distinguish
between customers and then these can be used to filter on the terms when translating for a
specific customer.
But if you share the terminology with your customer, maybe even charge extra for preparing a
document for them with their terminology, or provide it as a free additional service, then it
might make sense to have separate termbases for each customer.
The flexibility is there and it’s up to you how you use it. There are a few articles here that might
be interesting reading:
https://multifarious.filkin.com/2014/03/04/multitudinous/
https://multifarious.filkin.com/2016/10/17/square-pegs-in-round-holes/
• And a more general list of articles I have written related to working with terminology:
https://multifarious.filkin.com/tag/terminology/

86. www.sdl.com
facebook.com/sdlplctwitter.com/SDL linkedin.com/company/sdlplc/

87. Copyright © 2019 SDL plc. All Rights Reserved. The SDL name and logo, and SDL product and service
names are trademarks of SDL plc and/or its subsidiaries, some of which may be registered. Other
company, product or service names are the property of their respective holders..
This presentation and its content are SDL confidential unless otherwise specified, and may not be
copied, used or distributed except as authorised by SDL.
Software and Services for Human Understanding