Constructing a search string isn't a problem - the problem I hit was recognising that what I could see when viewing the file (unicode non-breaking spaces) wasn't what was in unviewed files so wouldn't be found by an "all files" search. I must include "beautify all files" in my workflow before doing any global S&R in the future, this will force the conversion. Having the editor automatically beautify the files on opening masked the issue - viewed files had been converted, unviewed ones hadn't.
Being pedantic wouldn't your
search find single as well as multiple non-breaking spaces ? I tend to use the
{2,} format for multiple spaces which is why I also use that format ({1,}) for "one or more", just habit I suppose.
BobC