As file contents I can see it being done if the number of spaces was always the same or limited to a few options ie always 1 space or 2 spaces:
contains abc[space]abc or
Are there other entries in the file? You have some options if granularized (hope that is a word) to the line level:
starts with abc and
ends with abc
Entry //abc** ends with abc
Entry //** matches abc.*abc
this would not work because the white space count may differ w each file
for example we want to run compliance on this file in RHEL
and want to make sure that all rhel boxes have this line
-a exit,always -F arch=b32 -S execve -F uid=0
if for some reason there is an extra space in there, the compliance will come back as non-compliant, but tis actually compliant and we dont want to spend time troubleshooting things like this.
I guess you are limited in using a different grammar file.
I think create an configuration file w/ hosts grammar file and then some thing like this will work.
"Configuration File Entry:/D/groupList.txt//abc"."Value1 as String (All OS)" = "abc" AND
I was running this on 8.5.0, as of 8.5.1 theres a new "ignore white space" compliance feature.