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

Error when Nickname mixed Arabic and English #273

Closed
zaher opened this issue Jun 3, 2018 · 5 comments
Closed

Error when Nickname mixed Arabic and English #273

zaher opened this issue Jun 3, 2018 · 5 comments

Comments

@zaher
Copy link

zaher commented Jun 3, 2018

I got error "Erroneous nickname" when set my nickname to this or even with number instead of English latter:
مjم

@DanielOaks
Copy link
Member

Hey Zaher! Unfortunately this is restrictions put in place by the Unicode people – specifically, the ones that made PRECIS and the UsernameCaseMapped profile. I suspect mixing scripts in that way is specifically disallowed by them. In addition, the restriction of IRC that the first character of a nickname can't be a number.

Because of that, I'm not really able to change it unfortunately 😅

@zaher
Copy link
Author

zaher commented Jun 3, 2018

No problem with numbers,
The weird thing that Oragono accepts unicode name like زاهر but if added one English latter it refuses it.

BTW I modified my client to use only English nickname.

@slingamn
Copy link
Member

slingamn commented Jun 3, 2018

Related discussions: #137 (directly relevant as it was a case where we were thinking about relaxing the PRECIS constraints), #178.

@DanielOaks
Copy link
Member

Ah yeah, the issue is that PRECIS specifically forbids things with BIDI markers in it iirc, which means that certain scripts (Japanese, Arabic, etc) might not work with others. Specifically, scripts written right-to-left and those written left-to-write may not work together – because of how those RTL and LTR languages work in Unicode, the extra characters can mess up and make the same visual letters look different in code.

@DanielOaks
Copy link
Member

Yeah I'm going to close this for now, since it's a dependency on the underlying PRECIS system unfortunately we can't solve this ourselves.

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

3 participants