Re:Falsehoods Programmers Believe About Names – With Examples
by gvx on Friday November 30, 2018 @07:39AM
(#18568642)
That point and point 40 ("People have names") can't be solved by technical means. There are two options here:
- You can make name fields optional for people without (representable) names - You can loosen what the field stands for to "what you want us to call you": for people who don't have a (representable) name, they can choose an alternative, without implying the user's (lack of) name is Wrong.
Re:Falsehoods Programmers Believe About Names – With Examples
by raverbashing on Friday November 30, 2018 @08:41AM
(#18568988)
Yes, you can't solve all cases but I'm betting someone will find a workaround for the sub 0.1% of those cases.
Much more rare than your system breaking because it chokes on the apostrophe in O'Donnels or something similar.
Re:Falsehoods Programmers Believe About Names – With Examples
by Piskvorrr on Friday November 30, 2018 @07:53AM
(#18568708)
This is not a design requirement - just something to keep in mind when designing a system. Otherwise, you're going to have a tough time requiring a `tussenvoegsel` form field in cultures where nobody knows what that is (spoiler: it's the Dutch "van " prefix; been there), or requiring that everyone has a middle name (USA), or a second surname (Mexico).
In other words, the usual problem is not "how do I fulfill all of these things?", but "how do I convince the USians that ASCII is not just insufficient, but that not even using Latin-1 won't do?"
"People’s names are all mapped in Unicode code points."
It seems like it is impossible to address all these points. Obviously there's no way for me to allow people to enter their names which don't have any known code point. So at some point you're always going to be saying "tough luck, you must adapt your name - or come up with something - that confirms to these constraints." And I am sure people are clever enough to do so.