You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The text was updated successfully, but these errors were encountered:
vkorablin
changed the title
Non-latin characters in character (b.net profile) name are displayed as url-encoded strings
Non-latin characters in character (b.net profile) names are displayed as url-encoded strings
Jun 22, 2015
If I can get eros to readd my old profile w/ Cyrillic letters in it, I'll make sure, but: possible source of the problem is in adding characters w/ the old client, where you have to provide a profile link manually. Some/most browsers will url-encode any symbols in the link that aren't representable in ASCII, then the server parses that url, extracts the url-encoded name from it and uses it as is.
To investigate: does adding through oauth subvert this issue? I expect it does, but have no means of testing yet due to eros not supporting more than one character per region on a single battle.net account.
Example: https://www.dropbox.com/s/xj4orw13dc8f90k/Screenshot%202015-06-23%2000.53.27.png?dl=0
EDIT: Happens in the old non-web client too.
The text was updated successfully, but these errors were encountered: