Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non-latin characters in character (b.net profile) names are displayed as url-encoded strings #14

Open
vkorablin opened this issue Jun 22, 2015 · 3 comments
Assignees

Comments

@vkorablin
Copy link
Contributor

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.

@vkorablin 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
@vkorablin vkorablin self-assigned this Jun 22, 2015
@sebneira
Copy link
Contributor

Reviving github issues! 💃

@vkorablin
Copy link
Contributor Author

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.

@sebneira
Copy link
Contributor

@vkorablin you can disable and reenable your character in erosjs. IIRC it'll update your data when it get reenabled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants