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

Verification / QA Checker 3.0: Grouped search expressions no longer working in Trados Studio 2021

This was a problem in an earlier version of Trados Studio that was corrected at some point. Now it's back. Example:

Description: ERR: 3.4b: Remove comma separator if not included in German

RegEx source: (\b[0-9]{4,9}\b)

RegEx target: $1

Condition: Grouped search expression - report if source matches but not target

Source unit: August 2020

Target unit: August 2020

A warning is thrown during verification despite the target matching the source exactly, as required. The idea here is not to translate 2020 as 2,020. This wasn't hitting in Trados Studio 2019 SR2 (most recent version), but it hit on my very first project after upgrading to Trados Studio 2021. That of course reminded me of a year or so ago when this was a problem and then fixed in 2019 I believe.




[locked by: Paul at 3:06 AM (GMT 1) on 23 Aug 2020]
Parents
  • To follow up:

    As expected, this affects other grouped search expression rules, for example:

    Description: ERR: x9: Check that target string matches source string with underscores

    RegEx source: ([0-9A-Za-z_]+_[0-9A-Za-z_]+)

    RegEx target: $1

    Condition: Grouped search expression - report if source matches but not target

    Source unit: 2.12_rev1

    Target unit: 2.12_rev1

    The idea here, of course, is that strings with underscores must match across the source and target. Only started having problems since the "upgrade" to 2021. Also having problems with other QA regular expressions, but I will make separate threads for those that are not grouped search expressions.

    ASIDE: I get the impression that the "basis" for the TS 2021 release was NOT TS 2019 SR2, at least not the latest version. My guess (and it's only a guess) is that an earlier version was used instead and the improvements made to TS since that version have been omitted. I also base this assessment on an autohotkey script I run for each new project. There's a telling "stutter" when you edit the settings of a translation memory in the project settings where the program kicks back to the main window from the Project Settings menu after you make a change. This occurred in an earlier version of TS as well but was repaired in a subsequent version.

    NOT ASIDE: I do have to say I'm quite disappointed and irritated that of all things to break, the verification rules are among them. This will cause a substantial amount of work for me that should have been able to be handled automatically, and in 2019 SR2 WAS handled automatically and correctly. I can only hope that an update/fix will be forthcoming in the next few days. :(

Reply
  • To follow up:

    As expected, this affects other grouped search expression rules, for example:

    Description: ERR: x9: Check that target string matches source string with underscores

    RegEx source: ([0-9A-Za-z_]+_[0-9A-Za-z_]+)

    RegEx target: $1

    Condition: Grouped search expression - report if source matches but not target

    Source unit: 2.12_rev1

    Target unit: 2.12_rev1

    The idea here, of course, is that strings with underscores must match across the source and target. Only started having problems since the "upgrade" to 2021. Also having problems with other QA regular expressions, but I will make separate threads for those that are not grouped search expressions.

    ASIDE: I get the impression that the "basis" for the TS 2021 release was NOT TS 2019 SR2, at least not the latest version. My guess (and it's only a guess) is that an earlier version was used instead and the improvements made to TS since that version have been omitted. I also base this assessment on an autohotkey script I run for each new project. There's a telling "stutter" when you edit the settings of a translation memory in the project settings where the program kicks back to the main window from the Project Settings menu after you make a change. This occurred in an earlier version of TS as well but was repaired in a subsequent version.

    NOT ASIDE: I do have to say I'm quite disappointed and irritated that of all things to break, the verification rules are among them. This will cause a substantial amount of work for me that should have been able to be handled automatically, and in 2019 SR2 WAS handled automatically and correctly. I can only hope that an update/fix will be forthcoming in the next few days. :(

Children
No Data