Curious how you’re handling capitalization QA for Defined Terms across tools without drowning in false positives. I’m on memoQ 10.5 with Verifika, using a regex to catch lowercase instances pulled from the termbase, but pluralized forms and quote encapsulation tripped it up on a 97‑page MSA last week. Any reliable patterns or workflows that survive Word export with Track Changes and preserve clause numbering?
On a 97‑page MSA I stopped fighting quotes by using Unicode quote classes in Verifika: “(?i)(?:\p{Pi})?\bYourTerm\b(?:\p{Pf})?(?:['’]s|s)?”, which handles curly/straight quotes and plural/'s. Pair that with memoQ 10.5 TB entries set to Case sensitive and it flags lowercase reliably; only caveat: Track Changes deletions can still trigger noise, @OP.
, this drives me nuts. @OP I stopped relying on regex and, after Word export, run PerfectIt with a tiny project style listing the “Defined Terms” (I include plurals/possessives like “Supplier(s)” and “Buyer’s”) — it reliably flags lowercase hits even inside quotes and handles revisions better than Verifika; https://intelligentediting.com. Small caveat: you have to seed the list once per big MSA, but it’s about 10 minutes — worth trying?
Quick tip, @OP: I stopped wrestling with patterns and tag each Defined Term in Word with a throwaway character style like “DefinedTerm,” then run one wildcard search for lowercase hits that excludes that style — works across plurals and quotes and survives export. Small caveat: if someone edits the term during review, re-run the styling macro before the final pass.
I duplicate the DOCX, accept all changes in the copy, run my capitalization checks there, fix the hits, then use Word’s Compare to rebuild a tracked version — keeps “Agreement” and friends consistent without Track Changes noise… Small caveat: Compare can shift a few comment anchors; @alexis_garcia91’s idea pairs well as a regex safety net so it doesn’t turn into whack‑a‑mole.
I stopped chasing regex () and in memoQ 10.5 I add each “Defined Term” twice: the proper-cased entry as normal and a lowercase entry marked Forbidden with morphology on, so QA catches agreement/agreements/'s without tons of noise. Then I leave Verifika out of caps and use it for other checks after Word export, since memoQ’s QA already nailed the 97-page MSA cases. Minor trade-off: you’ll need a quick CSV to bulk-add the forbidden lowercase variants, @OP.