Encoding causes PM issues

I have version 7.8 and we are using a full paid version of the forums.

I entered the username "Stupidalikeafox" for a new registered user. This worked fine.  The person logged in as this user and sent me a PM.

I notice when I pressed reply his username became "Stupidalikeafox" and pressing send informed me that the user was unknown.

Tried it again removing the "e" and replacing with an "e" and it worked fine.  Also searching for the user and then sending a PM to them works.

I looked in the Access database and noticed numerous times that characters are substituted "o" for "o" in varied fields.

Obviously this is an issue in the username and no doubt you can re-create it or I can send you our forum database.

Lastly it would never let me enter "StupidaLikeaFox" with the Capital "L", always defaulted to the "l".  This might seem petty but having the character case displayed is very important to our users.

Please let me know what is going on?????

Okay I can change the filter for the word "like" but effectively you need to change your code for the PM reply to put the  username back to an uncoded view in the screen.

For instance I can PM "Stupidalikeafox" straight out by entering it, from memory I can search for it and bring it down and send a PM okay. 

When you press the reply button on a PM from "StupidalikeaFox" the code that places the username in this field needs to strip your security characters out. Seems silly that I can send a PM directly using the standard word and that a newly formed reply will not place the original in.

Will you be putting this in a future release?