3 ms·
That just answers your own question isn't it? It's more work for backend developers to normalize things. If you only allow ASCII, no such work is required.
by kccqzy 8y ago
That just answers your own question isn't it? It's more work for backend developers to normalize things. If you only allow ASCII, no such work is required.
- Sammi 8y agoI don't think there is much of a hassle to implement this. I can only imagine a handful of lines necessary to handle this. Decide which normalization form, if any, you are going to use and then do the normalization in one place on the backend. And the benefit for the user to be able to use whatever characters in whatever language they are used to is immensely valuable for them. ASCII is extremely limiting and anglocentric. English is universal for people who communicate internationally, but imagine the amount of people who live their lives locally and are only used to writing in their own language. Requiring ASCII of them is unreasonable and one might be excluding a lot of people from using your system.