Audiosurf Air > Discussion

Can non-ASCII Characters Be Recognized On Usernames?

(1/5) > >>

GeoLuz:
There have been many unworkable URLs on AS that won't allow you to access a player's page due to non-ASCII characters such as Cyrillic characters. There also have been characters used to create fake accounts. Can the problem of unworkable URLs be fixed for Audiosurf Air?

blue_h3x:
Possible solutions:

1) All non a-z A-Z 0-9 characters removed (can be done with regex). This includes spaces (the PHP command trim() will remove spaces at the start/end of names(strings))

2) All non  a-z A-Z 0-9 characters converted to their URL safe form

3) A hash derived from the username used to view the profile.

Number 3 would be the easiest to implement that would allow anything to be entered, however creates none human recognisable URLs.
Number 1 would be the easiest that would leave the URLs as human readable.

Lebon14:
Personnally, your #2 is also a very good solution.  For exemple, a space's safe code is "%20".  Another exemple, "愛" (Ai; Love in Japanese) is "%E6%84%9B".  That can be a lot of work if you are going to make a databse out of this but, thanks to this page, I was able to offer "Ai"'s code :
http://www.w3schools.com/tags/ref_urlencode.asp

:)

blue_h3x:
#2 is easier than you'd expect ;) http://php.net/manual/en/function.urlencode.php

Although it does create a bit of a mess for fancy characters.

S.:

--- Quote from: blue_h3x on March 25, 2012, 06:23:06 am ---Although it does create a bit of a mess for fancy characters.

--- End quote ---
At least it allows us to 'customize' our nicknames. Though it's debatable to what extend you would want that. Personally I get pretty annoyed by people who use odd things in their Steam display name.

I'd vote for option 2. This will make some urls still human recognizable, while option 3 messes up all urls.

We'll see what Dylan does.

Navigation

[0] Message Index

[#] Next page