We receive a '�' symbol in the relay response instead of accents.
I am even not able to recreate a hash that matches the provided hash using the original symbol.
The characters are in the supported range, listed in the support article(Changes to Supported-Characters).
There was a related discussion at the end of a separate thread(Upgrading MD5 to newhash(SIM)), but unfortunately, I was not able to find a solution there.
Also, we have one more issue. When we send an address with two spaces, the second space is replaced with a '�' symbol in the relay response. The validation fails in this case, and it is not possible to create a matching hash after replacing a '�' with the original space.
This issue came up in a thread here and I developed a custom function to handle these characters. It’s been quite some time but the double spaces thing sounds sort of familiar. It has to do with encoding.
Your profile doesn’t have an IM button. Shoot me a message if you want to talk about this further.
I guess the short answer if you want it is to take whatever you get and reverse engineer the function to get you what you want. Read the post I linked. It has the one character I never could figure out how to deal with. I have something around 120 that I have used successfully.