@John M This seems like something that would be easy for Xojo to implement, so we don't have to wade through miles of code looking for places where strings are compared using = and then replacing = with a function would be tedious in the extreme, to say nothing of prone to mistakes.
Testing for equality with = is much faster than using String.Compare and I suppose we wouldn‘t want = to become less efficient when comparing strings. I have no idea what fixing = would entail with regard to speed. It might be preferable to normalize strings internally so any code could rely on canonically equivalent text to be represented by the same sequence of code points and bytes (always precomposed or always decomposed, whatever).
Until canonical equivalence is properly implemented throughout Xojo, using String.Compare for any text received from the outside world may yet be your best bet.
@John M Or is there some existing easy way to implement this?
I have tried converting the encoding from UTF8 to some other variant of Unicode and back, hoping the text would be normalized in the process, but to no avail.