Paul Hi Paul, any idea if this is already possible, or could be added to MT Enhanced Provider?

Michael Beijer 

It's not possible now, and we won't be doing any more work on the MT Enhanced Provider.  But don't worry... we've just split it up into two providers, one plugin for Microsoft and one for Google.  We did this for a few reasons:

1. we didn't write the original plugin and it's difficult to work on
2. it's not obvious to users who just want Google or just want Microsoft
3. the UI and UX needed improving, especially around Google with the AutoML

We have retained the concept of the "XML file" for both plugins and I guess we could look at adding a regular expression capability to it... maybe not for the first release but we could look at it.  In my head using back references might be better since I imagine the use of regex in any scenario will be designed to manipulate something you derive from the source (the txt you want to change, not the source text) and we probably need to have some control to tell the engine it is a regex and not text, but I don't see any reason why we couldn't do that.

We'll plan something in to look at it.

Michael Beijer 

It's not possible now, and we won't be doing any more work on the MT Enhanced Provider.  But don't worry... we've just split it up into two providers, one plugin for Microsoft and one for Google.  We did this for a few reasons:

1. we didn't write the original plugin and it's difficult to work on
2. it's not obvious to users who just want Google or just want Microsoft
3. the UI and UX needed improving, especially around Google with the AutoML

We have retained the concept of the "XML file" for both plugins and I guess we could look at adding a regular expression capability to it... maybe not for the first release but we could look at it.  In my head using back references might be better since I imagine the use of regex in any scenario will be designed to manipulate something you derive from the source (the txt you want to change, not the source text) and we probably need to have some control to tell the engine it is a regex and not text, but I don't see any reason why we couldn't do that.

We'll plan something in to look at it.

Wow, very interesting! This little app has proven extremely useful, what with it's very reliable ability to customize terms. 

Incidentally, I always use "post-lookup find/replace", rather than "pre-lookup find/replace".