Best practice to handle / sanitize usernames (accents, punctuation, ...)? -


Why would you recommend the best practice to handle or send usernames? In order to limit the Latin alphabet to France, Spain, Greece, ... you will receive period, dash, apostrops, ....

What we are doing, get information from the Facebook API We have got the username, if the user has set it, otherwise we take the name and change it to username (for example to log in later).

How have you managed it?

user names Full Unicode support in

If you are worried about cloning the use of Unicode characters, then you have automatically generated visual clues (next to many new user accounts, but replaced by the user icon) next to the name. Without).

If you still have to reduce the ASCII category, you can use the standard tool for generalizing Unicode text. They work on the basis of various Unicode equivalent principles:

It may be appropriate for people to accept letters in the Unicode range for those who give their lectures, but they The user account does not have to accept the same generalized form as the current one i.e. You can set / user / clamt, which will deny the creation of / user / clement and / user / client.


Comments

Popular posts from this blog

c# - sqlDecimal to decimal clr stored procedure Unable to cast object of type 'System.Data.SqlTypes.SqlDecimal' to type 'System.IConvertible' -

Calling GetGUIThreadInfo from Outlook VBA -

Obfuscating Python code? -