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.
Forbidden terms in QA check (F8) in TRADOS: question about termbase structure
Thread poster: Edward Bradburn
Edward Bradburn Germany Local time: 13:49 German to English + ...
Mar 24, 2020
Hi All,
I have a client who has terms defined in their termbase so that one headword in German has several translations in EN but only one is actually "preferred" -- the rest are "deprecated".
This sounds like a good idea in principle (it certainly adds context to changing terminology, which is very useful for old TMs) but when you check with F8 and make these deprecated terms actually forbidden in the QA search, TRADOS flags *any segment* containing these words as inco... See more
Hi All,
I have a client who has terms defined in their termbase so that one headword in German has several translations in EN but only one is actually "preferred" -- the rest are "deprecated".
This sounds like a good idea in principle (it certainly adds context to changing terminology, which is very useful for old TMs) but when you check with F8 and make these deprecated terms actually forbidden in the QA search, TRADOS flags *any segment* containing these words as incorrect. And it does not tell you where they are forbidden, either. Only searching "the other way around" (EN -> DE) lets you find the deprecated term.
Example:
I have these two terms in my TB, e.g.:
Schwarzbrot -> black bread defined as "preferred", rye bread defined as "deprecated" Roggenbrot -> rye bread defined, nothing else
I run an F8 search, stating that I want my termbase "deprecated" entries to be flagged as "forbidden".
If I now have a text with segments where Roggenbrot is translated as rye bread, TRADOS will flag this as wrong, because "rye bread" is flagged as wrong for a *totally different term*. It does not link to the Roggenbrot entry, it just marks it wrong. Not exactly useful.
This is not intuitive. TRADOS seems to use forbidden terms as a *global* "stop-word list", which is not what it should be doing. A forbidden word should be forbidden for a particular term (like in memoQ), not the whole text regardless of source context.
Hope I have explained this properly, it's really counter-intuitive, which is why I mention it.
Translate faster & easier, using a sophisticated CAT tool built by a translator / developer.
Accept jobs from clients who use Trados, MemoQ, Wordfast & major CAT tools.
Download and start using CafeTran Espresso -- for free
Create customer quotes and invoices from within Trados Studio
Trados Business Manager Lite helps to simplify and speed up some of the daily tasks, such as invoicing and reporting, associated with running your freelance translation business.