Essentially I'm wondering if the "replace" text used in the tag search/replace function (as well as the $RxReplace() virtual function) is processed for anything
other than the normal $nn backreference tokens?
In particular, the \U...\E switches common to RegExp replacements, where the text between \U and \E is converted to upper-case before being pasted in.
As a simple example, if I wanted to capitalize the first letter in a title after a dash mark ("-") I would use:
with the replacement text:
Testing with the title "rem-nant" should return as "rem-Nant", except in MB the returned string is "rem-\Un\Eant" which basically means the \U and \E regexp switches are ignored.
I also tested this with the virtual function $RxReplace(<Title>,"\-(.)","-\U$1\E") with the same result.
My original use case for this was more complex, but you get the idea. For comparison, I ultimately just used the regexp replace function in MP3tag to accomplish this, so I know the syntax is correct, but as MB supports regexp in most things, it would make sense for this too to work. Unless I'm missing something?
As this could be considered anything from a bug to an oversight or even a "feature" depending on one's point of view, I ask as a general query.