Term recognition window - only show allowed terms

I'm sorry but I can't seem to find the answer to this one in the RWS documentation/on Google.

If we have a long list of forbidden terms and we only want to see the good ones in Studio when translating, how can we do this?

I know how to make descriptive fields visible for terms, but this is not what I'm looking for.

THANK YOU!

emoji
Parents
  •  

    I have a slightly different view on things.
    I feel a termbase should showcase both approved and forbidden terms.

    If you remove forbidden terms out of your termbase entirely as  suggests, then how do you ensure users didnt start introducing terms interactivity/systematically mid translation that would have been classified as forbidden? Is this an exercise post translation??

    Studio does have the capability of putting a term QA on a term based on term status - so if the forbidden term does get used in error it will be picked up.

    Trados Studio verification settings window showing an error icon next to 'Check for terms which may have been set as forbidden' option.


    By going into the HitList settings you can also specify for more detail to come through as part of term recognition.
    As seen below I have 2 terms showing, but one is clearly marked forbidden while the other is approved

    Term Recognition window in Trados Studio displaying two terms, 'USB cable' marked as forbidden and 'photo printer' marked as approved.

    Defining your Termbase hitlist settings - is possible even for Language Cloud Termbases.
    And whats nice is you can set your ideal preferences. Save it as a template which others users can then implement.

    If you do continue with the notion of your term lists only contain approved terms, then I suspect you will become very dependent on the other term QA setting known as: Check for possible non usage of target terms. As seen in the screen prints above. 

    Also noteworthy information: 
    Depending on which technical solution you are using other options to help manager user settings could be done.

    Example with GroupShare you can set Filters, Layouts and even use Termbase classifications at user group level to ensure users see the right level of information.
    Making the idea of 1 complete termbase even more ideal - depending on the level of detail you need.
    What this means in practice. By configuration, users as part of Group A automatically gets to see all terms while users as part of Group B only sees approved terms.
    I always loved this concept because I could set a group of users up (Subject Matter Experts) who only work on pending approved terms and in this way they dont get overwhelmed with large term lists. And managing such detail as part of configuration makes it easier to manage and puts less dependency on the users themselves 

    I hope that some of this helps you explore whats best for you

    Lyds

    Lydia Simplicio | RWS Group

    _______
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 8:50 AM (GMT 0) on 19 Mar 2024]
  • Hi  

    As always, you provide some insightful information. Thank you!

    There are two main reasons why we do not include forbidden terms in our target language terms:

    1) It is inefficient. Imagine a made-up product called Visual Effects with the following terms provided in the termbase (target):

    Visual Effects: Approved

    VisualEffects: Forbidden

    Visual-Effects: Forbidden

    Visual effects: Forbidden

    visual effects: Forbidden

    visual-effects: Forbidden

    Visual-effect: Forbidden

    Using autocomplete during translation, you would have to pay very close attention that you choose the right approved term from the list of provided options. It takes effort, and with hundreds or thousands of terms, stopping and scrolling and selecting several times in a segment eats up valuable time when you can just select between correct terms (ideally just one) and move on.

    Trados Studio screenshot showing a list of terms with 'Visual Effects' marked as preferred and variations marked as deprecated. Autocomplete dropdown visible with term options.

    In a nutshell, I can't understand why we are even being offered the option of adding forbidden terms here. Here, the correct term is the first one (due to entry structure maybe?), but this has not always been the case, at least for us (again, maybe the term entry could be optimized on our side). Of course, if you select the wrong one, it should be flagged since it's forbidden, which is great, except that it leads us to reason 2, which is a true killer for us.

    2) A term forbidden in one context is forbidden in every context. That means for example:

    Trados Studio screenshot with a translation segment 'Visual Effects' highlighted in blue and a warning for forbidden term usage in the target text.

    This may not be the best example. A real-word example would be forbidding the English word "connection" for the German word "Schnittstelle" (usually "interface"). That words is now forbidden in EVERY context, i.e. you can never use it anywhere else, not just for the translation of Schnittstelle. So if I have the German word "Verbindung" 400 segments down, I will get an error every time I want to translate it (correctly, in most cases) with the word "connection". So basically, the word "connection" is banned from use, period.

    This has been my understanding of how this has worked up until now. Maybe I'm missing something, please let me know if so!

    Our workaround has been pointed out by Lydia. We have a second "Must" termbase, that we use to make sure that the most important terms are translated properly (check for non-usage). It's not the cleanest solution, perhaps, but it's a practical one.

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 10:07 AM (GMT 0) on 19 Mar 2024]
  •  

    Your examples and ongoing explanations is very true.

    Variations like VisualEffects vs Visual-Effects which are all set as Forbidden, does mean you are potentially faced with a bigger list of forbidden terms vs a list of approved terms.

    Some of the setting in Studio like the ones highlighted in the screen print below helps at times. However in many cases the differences are marginal and therefore these settings dont apply as expected.

    Trados Studio options menu with Verification selected, showing Search Settings. 'Allow overlapping terms' is checked. Sliders for 'Minimum match value %', 'Search depth', and 'Term repetition threshold' are visible.

    Also take into account, for some users where source terms are not consistent (VisualEffects vs Visual-Effects) but should be treated as approved, adds to the very specific use cases and how Termbases / configurations are setup. 

    I am also very accepting that term in context could drive a lot of false/positives. But I think the same could be true for managing the context of the source text.

    Would love to hear how other solutions solve the nuances of term variations (source and target) and what support is there for term context during translation. Just as we have CM from TM's Slight smile

    Lyds

    Lydia Simplicio | RWS Group

    _______
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 11:47 AM (GMT 0) on 19 Mar 2024]
Reply
  •  

    Your examples and ongoing explanations is very true.

    Variations like VisualEffects vs Visual-Effects which are all set as Forbidden, does mean you are potentially faced with a bigger list of forbidden terms vs a list of approved terms.

    Some of the setting in Studio like the ones highlighted in the screen print below helps at times. However in many cases the differences are marginal and therefore these settings dont apply as expected.

    Trados Studio options menu with Verification selected, showing Search Settings. 'Allow overlapping terms' is checked. Sliders for 'Minimum match value %', 'Search depth', and 'Term repetition threshold' are visible.

    Also take into account, for some users where source terms are not consistent (VisualEffects vs Visual-Effects) but should be treated as approved, adds to the very specific use cases and how Termbases / configurations are setup. 

    I am also very accepting that term in context could drive a lot of false/positives. But I think the same could be true for managing the context of the source text.

    Would love to hear how other solutions solve the nuances of term variations (source and target) and what support is there for term context during translation. Just as we have CM from TM's Slight smile

    Lyds

    Lydia Simplicio | RWS Group

    _______
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 11:47 AM (GMT 0) on 19 Mar 2024]
Children
No Data