2 ms·
> you don't have to worry that there is a 10 byte emoji or a turkish upper case i Excluding all emoji is silly but feasible (except for actual thorough custom
by HelloNurse 1y ago
> you don't have to worry that there is a 10 byte emoji or a turkish upper case i
Excluding all emoji is silly but feasible (except for actual thorough custom validation and error handling of all inputs), but excluding some uppercase and lowercase letters because you don't feel up to the task of processing them is demeaning lunacy.
- alkonaut 1y agoAgain, I'm now talking about "known" text in the programming context. Text that is neither user-input, or presented to a user. (E.g. column names. builtin function names in my toy spreadsheet. Whatever). Obviously for text that is both user-input and then displayed back again to users, you are in the other category. Apart from protecting against rendering mishaps and security etc, you probably just want to preserve what they write. But that was my point: 90% or more of the text you do is likely in the first category. And very rarely do you even have do deal with text in the second category.