I think it is not documented but a semicolon in a searchstring acts the same way as a space, but with the issue described below.
This issue isn't new for TC 11.51 but exists for a long time in TC.
Create 2 files with the following filenames:
A;B.txt
C;D.txt
Search for:
Code: Select all
"A;B.txt";"C;D.txt"
But if the entire search string contains a space character anywhere (as separator or as part of a filename), the issue doesn't occur.
And the issue only happens for the fist quoted string that starts at the beginning, so the following example doesn't have the issue:
Code: Select all
Q.TXT;"A;B.txt";"C;D.txt"