UTRS / utrs

Unblock Ticket Request System
https://utrs.wmflabs.org/
14 stars 13 forks source link

Non-latin characters in account names #100

Open Salvidrim opened 8 years ago

Salvidrim commented 8 years ago

This was previously an issue which we fixed for the permissions-check script (#58) however a point was left unresolved and today it has been an active problem.

"Appellant account names for the purpose of detecting if blocked?"

Example: Appeal 16109

The account name is "User:ゼーロ"

Here is the user's note: "My username is "zero" in katakana, but the form won't submit if I enter it in that script. I'll try here: ゼーロ. It might be corrupt on your end though.

I tried to submit a ticket before. I got an email back asking me to confirm my username, which I responded to. Then later I got an email saying I had not responded. Well, I had... Check your spam folder perhaps? I checked mine for further emails and there were none. You can also write on my talk page since I can still edit that."

Note that in the user's message the Katakana is rendered in fhe form "& # 1 2 4 7 6 ;" minus the spaces

dqwiki commented 8 years ago

@TParis would your code used before work in this case? Because all I have to do is switch my encoding to UTF-8 on my computer, change some DB values (in appeal and banList) and it worked, just crapped out when using the default encoding.

TParis commented 8 years ago

Yes,  but not today

Sent via the Samsung Galaxy Note® 4, an AT&T 4G LTE smartphone

-------- Original message -------- From: dqwiki notifications@github.com Date: 7/13/2016 14:58 (GMT-10:00) To: UTRS/utrs utrs@noreply.github.com Cc: TParis tparis@ufpfleet.org, Mention mention@noreply.github.com Subject: Re: [UTRS/utrs] Non-latin characters in account names (#100)

@TParis would your code used before work in this case? Because all I have to do is switch my encoding to UTF-8 on my computer, change some DB values (in appeal and banList) and it worked, just crapped out when using the default encoding.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.