Under Community Review

Studio behaviour with forbidden terms

We have enabled the check in terminology verify Studio for deprecated terms
When we translate a segment which doesn't contain the source term and we use the deprecated term an error appears corresponding to the line
What we expected was that only in case we had the source term corresponding to the deprecated target the message appeared otherwise lots of fake errors are created.

 
We cannot give for granted that a term deprecated when associated to a term must be considered always deprecated.
Logos Help Desk
Parents

  • This has worked in memoQ for years.

    It's a simple, single check box and the deprecation handling works exactly as expected.

    So you can have

    - a blacklist, e.g. if you are translating a marketing text and want no old product names in there at all

    - or a deprecated-per-term setup, where you have new terms for some things but these are not global

    There's simply zero excuse for it to not work in Studio.

    I have a client who has painstakingly set up a large Trados termbase for this and we, as translators, now regularly generate F8 reports with thousands upon thousands of errors, of which about 99.5% are false alarms. Utterly useless.

Comment

  • This has worked in memoQ for years.

    It's a simple, single check box and the deprecation handling works exactly as expected.

    So you can have

    - a blacklist, e.g. if you are translating a marketing text and want no old product names in there at all

    - or a deprecated-per-term setup, where you have new terms for some things but these are not global

    There's simply zero excuse for it to not work in Studio.

    I have a client who has painstakingly set up a large Trados termbase for this and we, as translators, now regularly generate F8 reports with thousands upon thousands of errors, of which about 99.5% are false alarms. Utterly useless.

Children
No Data