Trados Studio
Trados GroupShare
Trados Business Manager
Trados Live
MultiTerm
Passolo
Speech to Text
Managed Translation - Enterprise
MultiTrans
TMS
Translation Management Connectors
WorldServer
LiveContent S1000D
Contenta S1000D
XPP
Tridion Docs
Tridion Sites
Language Weaver
Language Weaver Connectors
Language Weaver Edge
Language Developers
Tridion Docs Developers
Xopus Developers
Community Help
RWS User Experience
Mercury
RWS Community Internal Group
RWS Access Customer Portal
RWS Professional Services
RWS Training & Certification
Style Guides
RWS Enterprise Technology Partners
Trados Academic Partners
Trados Approved Trainers
XyUser Group
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic Tridion Docs User Group
Tridion Docs Europe & APAC User Group
Tridion UK Meetup
Tridion User Group Benelux
Tridion User Group New England
Tridion User Group Ohio Valley
Tridion West Coast User Group
WorldServer User Group
MultiTerm Ideas
Passolo Ideas
Trados GroupShare Ideas
Trados Studio Ideas
Language Weaver Ideas
Language Weaver Edge Ideas
RWS Language Cloud TMS Ideas
RWS Language Cloud Terminology Ideas
RWS Language Cloud Online Editor Ideas
Managed Translation - Enterprise Ideas
TMS Ideas
WorldServer Ideas
Tridion Docs Ideas
Tridion Sites Ideas
LiveContent S1000D Ideas
XPP Ideas
Events & Webinars
To RWS Documentation
To RWS Support
Detecting language please wait for.......
Whereas \w+,\s(\w+) is processed without problem, the "complex" \w+,\s(\w+\s\d{1,2}) could not processed within an acceptable time.
Display Filter had no problem with the "complex regex", but cannot be used in my case because I need to make a replacement.
The "solution" was to replace \w with [a-z] (case-insensitive). Even [a-z0-9]+,\s([a-z0-9]+\s\d{1,2}) brought Find to its "knees".
This behaviour concerns Studio 2019.
The regex
\w+,\s(\w+\s\d{1,2})
found the text a, aaa 12
after a gap of ~300 segments instantaneously in my Trados Studio 2019.
Is it a number of segments big enough to notice the lag?
Strange. My document has 3000 segments; the first match at segment 153 took 55 seconds (starting at the first segment)! Even the search starting at segment 135 (3 lines) took 20 seconds, although starting at segment 136 (1 line, as were all intervening segments) was instantaneous.
Whether there is something special in segment 135 or a healthy restart will solve the problem.
I checked the same regex in Notepad++ and it took a noticeable time, but certainly much less than a second, to process 1.7 million chars. I've used some complex regexes taking many seconds to complete, but there is nothing special with yours.
Restart brought no improvement. Display Filter returns instantaneous results.
It picks my curiosity…
If you create a simplified version of your document that fails in the regex Find, please post it and I'll test it.