• State Suggested Answer
  • +2 person also asked this people also asked this
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 434 subscribers
  • Views 1381 views
  • Users 0 members are here
Options
Related

F8 with forbidden terms does not work as expected

Edward Bradburn

Hi Folks,

I'd like to flag this up again from a similar post a few years back in the MultiTerm forum:

https://community.sdl.com/product-groups/translationproductivity/f/multiterm/6328/what-are-the-proper-verification-settings-for-detecting-forbidden-terms-in-terminology-verifier-ts-2015

The problem is that SDL Studio does not check forbidden terms correctly.

That is: it does not check forbidden terms on a term-by-term basis but globally.

This makes it useless except for terms that should not be in the text at all, i.e. a kind of "stop list".

While I imagine this does have limited use - such as forbidding use of the word "enable" in English - the much more useful application of stopping the use of a word for a specific term is not provided, and this is counter-intuitive since this is exactly what is expected for a forbidden term search working on a per-term basis.

Is there anywhere where this bug - since I believe it to be one - could be reported?

As a footnote to this bug report, it would make MUCH more sense in my opinion if we could simply search for terms with a specific status and not merely "forbidden". This would make term bases much more useful. A document could be searched for all terms flagged for SEO use, for example, or for user interface terminology. This could all be stored in parallel in the term base.

At the moment, this simply does not work (as expected).

Added footnote.
[edited by: Edward Bradburn at 9:28 AM (GMT 1) on 14 Sep 2021]
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    Just flagging this up again since Trados 2021 still has the same utterly illogical behaviour and it is still immensely frustrating for the client and for myself.

    tl;dr: Trados considers the target term for a pair of deprecated terms as a stop list and flags them in the entire document, ignoring the reference term, so if you set up this:

    - Bereich -> Department
    - Bereich -> Range (deprecated)

    and then run a terminology check including deprecated terms, Trados Studio will flag every single mention of "Range", whether "Bereich" is present in the source language or not. It will in fact even flag it if "Department" is (correctly) present in the source language.

    (tbh, the whole terminology thing/F8 in Trados is an absolute nightmare: everything done live so you have to wait while it updates, no possibility of bulk deleting terminology messages, etc. etc.)
    emoji
Reply
  • 0

    Just flagging this up again since Trados 2021 still has the same utterly illogical behaviour and it is still immensely frustrating for the client and for myself.

    tl;dr: Trados considers the target term for a pair of deprecated terms as a stop list and flags them in the entire document, ignoring the reference term, so if you set up this:

    - Bereich -> Department
    - Bereich -> Range (deprecated)

    and then run a terminology check including deprecated terms, Trados Studio will flag every single mention of "Range", whether "Bereich" is present in the source language or not. It will in fact even flag it if "Department" is (correctly) present in the source language.

    (tbh, the whole terminology thing/F8 in Trados is an absolute nightmare: everything done live so you have to wait while it updates, no possibility of bulk deleting terminology messages, etc. etc.)
    emoji
Children
No Data