Highlighting Double Spaces etc

[bigcitydealer]

I'm in the process of removing double spaces.
I use the filter function to show only those files that contain them and I also have an action that removes them.
Is there a way to show where they are for example highlight them so I can see them before actioning?
If not, would be nice to have (at least for me)

[ohrenkino]

There is no function to highlight any characters or other criteria that lead to a hit when filtering.
See also this discussion on the pros and cons of highlighting filter hits:

REQUEST: filter highlight

I would like to propose one addition: an option for the filter [when putting a search value in the box] not only be able to cut out [hide] unwanted files, but to somehow highlight them on the list of [all] displayed files The old method should be retained. But let's say clicking on the "Filter" sign could switch it from old method of filtering to the new one: from hiding unwanted files to highlighting the wanted ones

[LyricsLover]

@bigcitydealer

Is there a way to show where they are for example highlight them so I can see them before actioning?

I'm just curious:
Why should this be necessary?

If you are looking for ZZ, it should not matter where ZZ occurs.
IF it is important for you, you should define the search criteria more precise, like
"It must not be at the start or the end of the tag"
or
"It must not be followed by more space characters"
or whatever you think should be an exception.

[bigcitydealer]

Until I see why the double spaces have occurred I won't be able to decide how to define the action.
I'm usually quite meticulous about tagging and was surprised when there were so many.
One strange reason was if the artist or title etc contained / for example Disco / Party after converting tag to filename the / would be replace by a space therefore making a double space.

[LyricsLover]

@bigcitydealer

after converting tag to filename the / would be replace by a space therefore making a double space.

I doubt that this is true.
Tag -> Filename is only changing the filename. Nothing else.

Or do you mean that the filename contains two spaces (one as replacement for the invalid slash)?

Update 15.30 Uhr
I striked through the missleading word "replacement" in my above text. There is no "replacement" for invalid characters in windows filenames using Convert Tag -> Filename by default. Such invalid characters will be ignored and skipped.

[ohrenkino]

The slash is no valid character for a filename.
Without any further intervention by the user, the / is simply ignored.
If you use $validate() and set a space as replacement character, you get that.
If you want to see if there e.g. the artist field with leading or trailing spaces, you could use this
Filter: "$if($eql($len(%artist%),$len($trim(%artist%))),1,0)" IS 0

[LyricsLover]

@ohrenkino

Without any further intervention by the user, the / is simply ignored.

Exactly.

If you have
Disco␣/␣Party
in your title and create a filename with this content, only
Disco␣␣Party
remains (with two consecutive blanks), because the invalid slash will be ignored/skipped.

This is also true for all other invalid (Windows) characters in filenames:
* " / \ < > : | ?

[bigcitydealer]

Is there a way to stop it substituting the / (or other invalid Windows characters) for an additional blank?

[ohrenkino]

There is no additional blank as the blanks come from the blank in front of the slash and behind it.
If you want to remove all the double-blanks from a string, (even a complete filename), use the scripting function $replace(<string>,..,.) - where the dots represent a space character for better visibility as the forum formatter swallows several consecutive blanks

[bigcitydealer]

Ah yes of course...
Thanks for your help