• State Suggested Answer
  • +2 person also asked this people also asked this
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 435 subscribers
  • Views 907 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 Reply
  • 0 in reply to Daniel Hug

    Hi Daniel,

    Voted!

    And yes, I thought it would be fairly simple to create a new termbase without the deprecated terms but I have not discovered how to yet.

    Anyway, it's a client project and client termbase. Everything is set up neatly and it should work.

    All Studio needs to do is check each segment and see if the source term is a) present on the left and b) matches a forbidden target term on the right.

    That is, after all, what it does for a normal term check, except it checks for any term present rather than one with a specific status.

    If Studio applied the same logic to the normal term match, it would flag no errors at all as long as the term was present somewhere in the target language segments in the entire document.

    Cheers,

    Ed
Children