Trados Studio
Trados Live Essential/Live Team/Enterprise
Trados GroupShare
Trados Business Manager
Passolo
MultiTerm
RWS AppStore
Connectors
Beta Groups
Managed Translation
MultiTrans
TMS
WorldServer
Language Weaver
Language Weaver Connectors
Language Weaver Edge
Tridion Docs
Tridion Sites
LiveContent S1000D
XPP
Language Developers
Tridion Docs Developers
Community Help
RWS User Experience
Internal Trados Ideas Community
Mercury
RWS Community Internal Group
RWS Professional Services
RWS Training & Certification
Style Guides
RWS Campus
RWS Enterprise Technology Partners
Trados Approved Trainers
XyUser Group
ETUG (European Trados User Group) Public Information
Nordic Tridion Docs User Group
Tridion UK Meetup
Tridion West Coast User Group
Trados Studio Ideas
Trados GroupShare Ideas
Trados Live Team Ideas
Trados Live Essential Ideas
Trados Live Terminology Ideas
Trados Enterprise Ideas
Trados Online Editor Ideas
Trados Business Manager Ideas
MultiTerm Ideas
Passolo Ideas
RWS Appstore Ideas
Tridion Docs Ideas
Tridion Sites Ideas
Language Weaver Ideas
Language Weaver Edge Ideas
Managed Translation - Enterprise Ideas
TMS Ideas
WorldServer Ideas
LiveContent S1000D Ideas
Contenta S1000D
XPP Ideas
Events & Webinars
To RWS Support
Detecting language please wait for.......
A discussion was started today in ProZ (http://www.proz.com/forum/sdl_trados_support/309565-regex_f_r_question_trados_2015.html) that has brought to light several issues with regex in Find/Replace Operations that, if I remember correctly, are not new but still present even in Studio 2017.
I thought I'd start a thread here to get the discussion going with people who may be monitoring the SDL Community but not the ProZ Trados forum.
Some of the issues discussed in the ProZ thread include:
- Some segments are skipped during the Find operation for no apparent reason
- Some segments throw an error saying that the "Segment start/end cannot be deleted" when attempting to execute a replacement
- Tags are ignored in the Find/Replace operation
- [ cannot be used in the Replace field (although including both the opening and closing brackets works); using \[ will naturally result in \[ being inserted in the replacement, instead of the bracket being escaped
- ^ is ignored as a start of segment/string anchor during the Find operation
- Find/Replace stops responding after several of these operations