# data[].attributes.headline
SDL Trados Studio - where to look for help

# data[].attributes.subject
SDL Trados Studio - where to look for help

# data[].attributes.body
October 2021
From time to time SDL Trados launches an update that makes many users feel lost. Because Studio is an app I use everyday, I would like to recommend a few pages to look for help:

# data[].attributes.body
Recommended not only for beginners, but also for regular users. First of all, one can find there playlists divided between different Studio versions - wonderland for those who love being up-to-date with updates! Because SDL Trados has so many different options, it is worth checking the channel to discover what more the programme offers.
I personally recommend comments section - each user has her/his own way of dealing with a problem.

# data[].attributes.attachment_link.keywords[]
"sdl trados studio 2017" "sdl trados studio" trados "translation memory" "cat tools" "translation software" "trados tips" "trados tutorial" "adaptive machine...

# data[].attributes.attachment_link.description
Translation productivity software Delivering translations and content localization with accuracy and speed is a key challenge for any translation professional. This is why translators and localization teams use Computer Assisted Translation (CAT) tools to help them work quickly and manage their translation jobs more efficiently.

# data[].attributes.headline
Proz.com - website providing answers to all questions

# data[].attributes.subject
Proz.com - website providing answers to all questions

# data[].attributes.body
IT guys tend to call users "użyszkodnik" instead of "użytkownik" - not only fancy, but a true name. That's why before asking them for help, it is worth trying to find a solution on one's own. Proz.com is a website full of practical knowledge, so when one has an issue with Trados, it is possible that it was previously encountered by someone and described on proz.com (sometimes even IT guys look there for answers...).

# data[].attributes.attachment_link.readable_text
This site uses cookies. Some of these cookies are essential to the operation of the site, while others help to improve your experience by providing insights into how the site is being used. For more information, please see the ProZ.com privacy policy.

# data[].attributes.attachment_link.description
This site uses cookies. Some of these cookies are essential to the operation of the site, while others help to improve your experience by providing insights into how the site is being used. For more information, please see the ProZ.com privacy policy.

# data[].attributes.headline
Last but not least - official SDL Trados website

# data[].attributes.subject
Last but not least - official SDL Trados website

# data[].attributes.body
Honestly speaking, the official Trados website is always the last place where I look for help. In my company it is said that any impolite answer to an email sounds like "an answer from Trados dungeons" and I couldn't agree more. As long as their articles are very comprehensive and well-written, their customer service is mediocre, that's why I wouldn't recommend personally asking them for help.

# data[].attributes.attachment_link.readable_text
Support for everyone

RWS offers a wide range of technical and non-technical assistance programs and support to help you get the most from your RWS translation software products.

Whether you are a translator, language service provider (LSP) or a corporation, we offer a variety of options to fit your needs - from a rich library of online support resources to quick access to community support provided by other Trados Studio users or you could take advantage of a Support and Maintenance Contract which gives you direct contact to a professional technical support team. RWS's support offerings are designed to help you be more efficient and successful productive with our products.

# data[].attributes.attachment_link.description
Support for everyone RWS offers a wide range of technical and non-technical assistance programs and support to help you get the most from your RWS translation software products.

# data[].attributes.body
November 2021
As a translation bureau worker, I know how efficient keyboard shortcuts are - it is worth having a note on them.

# data[].attributes.body
CTRL + O -> open package
CTRL + ENTER -> confirm segment and update TM
CTRL + INS -> copy source to target
ALT + DEL -> clear target segment
F3 -> source concordance
CTRL + SHIFT + F3 -> target concordance
F7 -> spellcheck (current file)
F8 -> QA check (current file)

# data[].attributes.body
It is possible to customise the existing shortcuts, and add new ones for unassigned commands under:
FILE - OPTIONS - KEYBOARD SHORTCUTS

# data[].attributes.body
According to ISO 17100, taking shortcuts is not recommended. However, when it comes to working in SDL Trados Studio, translation bureaus positively insist that translators use every time-saving trick.

# data[].attributes.headline
An update is done - better safe than sorry!

# data[].attributes.subject
An update is done - better safe than sorry!

# data[].attributes.body
Based on my own experience, it is better to wait a few months before switching from an older Studio version to the newest one. There are often some glitches in the new version, because Trados tends to treat users as testers. So, some problems are only found by real users, the corrections to the programme are made, after some time Studio has the proper quality and that is when it is worth switching to the newest version.

# data[].attributes.body
December 2021
Creating such a report is very easy and not much time consuming, that is why it is recommended to create such report even when we receive stats alongside the project to translate.

# data[].attributes.body
When having the package opened, we right click on it - batch tasks - analyse files.

# data[].attributes.body
There is a short description of what this function does, we click "next".

# data[].attributes.body
And another we can see another window, where we can choose between different options:

# data[].attributes.body
After clicking "finish" the report is being generated. The programme creates the analysis for each separate xliff and for the whole project. The report can be found in "reports" section.

# data[].attributes.body
First of all, it is worth comparing the generated report with the one received from the Client. Second of all, it is advised to check whether the expected turnover is correct. Third of all, based on the wordcount in each fuzzy matches threshold one should estimate how much time the translation will take, and last but not least - confirm the DD.

# data[].attributes.headline
How does machine translation affect fuzzy matches and the translation price?

# data[].attributes.subject
How does machine translation affect fuzzy matches and the translation price?

# data[].attributes.body
December 2021
There used to be a rumour, in which many people still believe, that machine translation is a "tool" used by translation bureaus to save money and pay less to the translators. But is it really so?

# data[].attributes.body
The idea of the MT is that it is implemented into each empty segment, what means that in a file propagated with MT should be no no matches. As a result, all no matches are moved to 50%-74% category.
The picture presents statistic of the file propagated with MT.

# data[].attributes.body
What is post-editing price based on?

# data[].attributes.body
The most common way of calculating the price of post-editing is doing it per hour rate. These rates differ between languages, specialisations and translators. Quite surprising is that sometimes rates for translation and post-editing are the same!

# data[].attributes.headline
Post editing price based on fuzzy matches

# data[].attributes.subject
Post editing price based on fuzzy matches

# data[].attributes.body
Usually for Asian languages it is advised to calculate the post-editing price the same way the translation is calculated. As mentioned before, there are no no matches when MT is implemented, what affects the general price.
When translator is new to post-editing, his/her rate for this service is often calculated based on the fuzzy matches, because it is more economical.

# data[].attributes.body
Calculations of post-editing price based on discount are used least often. The rule here is simple - no matches are left as no matches, the price is calculated as if translation was being done and from this sum 20-30% is deducted.
This system is either too beneficial for the translator or for the client, that's why it is avoided.

# data[].attributes.headline
How to make sure that TB used is being compliant with the terminology requested by the Client?

# data[].attributes.subject
How to make sure that TB used is being compliant with the terminology requested by the Client?

# data[].attributes.body
January 2021

# data[].attributes.body
Server based TBs are very popular in translation word, however often they are the cause of many complaints. The bigger the TB is, the longer its update takes and when the update is being done, the TB is unavailable. Because in translation world services are often "time-sensitive", it cannot happen that for some period of time translator cannot do his/her work. That is why file-based TBs are being created.

# data[].attributes.headline
What are file based TBs and are they solution to all problems?

# data[].attributes.subject
What are file based TBs and are they solution to all problems?

# data[].attributes.body
File based TB is a file containing TB entries - sounds simple, but only in theory. In real life TBs are huge files requiring good computer software to work smoothly. They often cause Studio mishaps, "not responding" error and looking for term is very time-consuming. However, a bird in the hand is worth two in the bush, that is why is some situations the use of file based TB is recommended.

# data[].attributes.headline
How to limit terminology issues in SDL Trados Studio?

# data[].attributes.subject
How to limit terminology issues in SDL Trados Studio?

# data[].attributes.body
We all know that terminology is crucial in translation and without it the proper translation quality cannot be reached. In order to ensure the right quality, the MT hitlist may be installed. Each translation genre has its own MT hitlist. In my case, the MT hitlist profiles are updated regularly to ensure that the correct terminology choice is being made.

# data[].attributes.headline
How to install MT hitlist - step by step

# data[].attributes.subject
How to install MT hitlist - step by step

# data[].attributes.body
January 2021 (based on tests done between June and September)
The MT hitlist profiles will only work if the Studio interface language is the same as what it was when the profile was created. For this reason it is very important to ensure that the profile you use is the correct one for your Studio interface language.

# data[].attributes.body
If you do not have your Studio set to your preferred interface language, please do so now. With Studio open go to View > Use Interface Language:

# data[].attributes.headline
Choose the interface language that you prefer and press OK:

# data[].attributes.subject
Choose the interface language that you prefer and press OK:

# data[].attributes.body
(if your language isn’t in the list, please choose one that you are comfortable with)

# data[].attributes.headline
Studio will have to reload for the change to take effect:

# data[].attributes.subject
Studio will have to reload for the change to take effect:

# data[].attributes.body
You can only change or add an MT hitlist profile from inside the Studio Editor pane. Please set up the file-based termbase and open your Studio files for translation.

# data[].attributes.body
When you open your files for translation, the terminology entries in the term recognition window may look something like this:

# data[].attributes.body
This TB has a lot of information about each term that remains hidden unless the MT hitlist profile is set up properly.

To set it up, please press the Hitlist Settings button:

# data[].attributes.body
When this window opens, please press Load:

# data[].attributes.body
Then, the correct hitlist for your interface language has to be chosen

# data[].attributes.body
When the following window opens again, please press OK:

# data[].attributes.body
The term recognition window should now show much more information (the colors may vary depending on your settings)

This is now how the term recognition displays for one of the segments:

# data[].attributes.body
The term entries should show a definition and the status of the term either preferred or accepted (Vorzugsterm or Zugelassener Term):

# data[].attributes.body
This way you brought yourself in conformance with high quality TB usage standards.