RegExp & UTF-8 in search dialog should be mutually exclu

[now]

If I first check the “RegExp” option in the “Find Text” part of the dialog and then the “UTF-8”, the “RegExp” option is unchecked. This is very confusing, especially as I can then check the “RegExp” option again.

Either “RegExp” and “UTF-8” can be enabled at the same time, in which case “RegExp” shouldn’t become unchecked when enabling “UTF-8”, or, as soon as either option is checked, the other should be disabled.

Even better, switch to a regular expression library that supports more encodings (“UTF-16” also unchecks “RegExp”, but these options are at least mutually exclusive).

[StatusQuo]

Confirmed & agree.

From the Help about checkbox "UTF8":

Code: Select all

Note: At the moment, all UTF8-searches are case sensitive (due to limitations of the used search function).

Maybe the UTF8 option should have influenced the checkbox "case sensitive" instead then (forced to be on/maybe greyed out)?

In the help I found no comment like "Unicode/UTF8: can't be used together with RegEx option" or similar.
Preventing incompatible options is generally good IMO (and needs no translation ), but could be clearer.

[StatusQuo]

Not changed in TC 7.03.

[ghisler(Author)]

This problem has been postponed to TC 7.5 because I'm still looking for a way to make RegEx work with UTF-8.