This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Other verification rules (QA checker) not working in Trados Studio 2021

For related information, see here:

https://community.sdl.com/product-groups/translationproductivity/f/studio/30792/verification-qa-checker-3-0-grouped-search-expressions-no-longer-working-in-trados-studio-2021

Not sure why this QA rule broke, but I suspect it may have to do with a change in how Trados Studio 2021 deals with placeables. I'm not sure, however, since the problem occurs even after I disable every checkbox in the new TM settings / Language Resources page. This rule worked with no problems in previous versions of Trados Studio:

Description: WARN: x4: Remove extra full stop at end of sentence

RegEx source: (\.|Lizenz|erweitert werden|\.\.\. klicken)\.$

RexEx target: \.\.$

Condition: Report if target matches but not the source

Source unit: Eine Super Speed Übertragungsrate (5 GBit/s) ist nur mit USB 3.0 möglich.

Target unit: The SuperSpeed transfer rate (5 Gbit/s) is only possible with USB 3.0.

The idea is to prevent two full stops at the end of the target segment except under very specific conditions. Broke with the upgrade to TS 2021.

Next example:

Description: ERR: 3.4b: Add comma separators if included in German

RegEx source: (\b(?<!\.)[1-9]\.[0-9]{3}(?!\.)\b|\b(?<!\.)[1-9][0-9]\.[0-9]{3}(?!\.)\b|\b(?<!\.)[1-9][0-9]{2}\.[0-9]{3}(?!\.)\b|\b(?<!\.)[1-9]\.[0-9]{3}\.[0-9]{3}(?!\.)\b|\b(?<!\.)[1-9][0-9]\.[0-9]{3}\.[0-9]{3}(?!\.)\b|\b(?<!\.)[1-9][0-9]{2}\.[0-9]{3}\.[0-9]{3}(?!\.)\b)

RegEx target: (\b(?<!\,)[1-9]\,[0-9]{3}(?!\,)\b|\b(?<!\,)[1-9][0-9]\,[0-9]{3}(?!\,)\b|\b(?<!\,)[1-9][0-9]{2}\,[0-9]{3}(?!\,)\b|\b(?<!\,)[1-9]\,[0-9]{3}\,[0-9]{3}(?!\,)\b|\b(?<!\,)[1-9][0-9]\,[0-9]{3}\,[0-9]{3}(?!\,)\b|\b(?<!\,)[1-9][0-9]{2}\,[0-9]{3}\,[0-9]{3}(?!\,)\b)

Source unit: max. 78.000 (random)

Target unit: Max. 78,000 (random)

Condition: Report if source matches but not the target

Error: Source matches count 1, target matches count 0

According to my online checker site, http://regexstorm.net/tester, the target matches as well. This is also backed up in the fact that I never got this error before for these units until the upgrade to TS 2021. We get these types of units very often and never had a QA problem before.




[locked by: Paul at 3:07 AM (GMT 1) on 23 Aug 2020]