Under Community Review

Term recognition - is there any chance of re-engineering?

Hi!

The term recognition window - I think one of the most used  in Studio - seems not having evolved since years. While the Termbase view has been developed further, the Term Recognition window has been struggling with the old diseases. Neither the display nor the functions are satisfactory.

Only with simple term lists you can work well with, but as soon as you add fields and definitions, they are not displayed correctly. An info text, which you add as an own field to the term, does not break and runs out of the picture. If you program the break in Excel, the text breaks, but the space between 2 term entries is limited, so that the info text is not displayed.

Or did I missed something?

 Screenshot of Trados Studio Ideas term recognition window showing a term entry with poorly formatted info text running out of view.


Features for the future:

- better design (see Termbase viewer)

- better field design (see termbase viewer)

- better functionality (e.g. option to show also other languages than the one in the project)


Best regards

Burim

Burim Bektesi

  • One more, that I also have posted as an own idea:

    -  allow different settings for each termbase

    I don't know about you, but we often create an own termbase with HMI texts. So I need the term recognition to show these entries only if they are 100% identical (or 99%). While I would like my standard termbase to show terms starting from 80 % similarity.

  • It would be great if everyone would post his ideas/wishes for new functions here... I for my part would like these to be implemented in term recogniton:

    - Better all-over design -> see the term base viewer that has been redesigned.

    - Displaying fields and their contents -> show additional information in an acceptable design.

    - Forbidden words -> optionally show forbidden words in other color (red) or even better: mark the forbidden word on the fly in the target segment.

    - Second language terms -> optionally show e.g. English target terms as reference, even if I translate German > French.

    - Termbase working for all languages -> we often create a termbase with the source term and information as the "target term". But we always have to create such a termbase per language, instead of allowing us to use ONE for all languages (similar to AnyTM).

    - 1 file per Termbase -> instead those 5 or 6 files... it hast worked for the transition from the old workbench.

  • don't forget to vote for your own idea