I think you're missing my point. Having relaxed standards, such as I outlined, will account for nearly all special cases for a target audience that is reasonabl

I think you're missing my point. Having relaxed standards, such as I outlined, will account for nearly all special cases for a target audience that is reasonably homogeneous. Of course if you are designing a global facing application, then yes, you need to account for a wider range of possibilities. But for many applications designing around cultural norms, but being liberal about what you accept, is perfectly acceptable where the benefit of accommodating for low-probability cases does not justify the costs. And, like I mentioned, in cases for applications targeted towards a homogeneous group, for those that have names so far outside the cultural norms that even liberal standards cannot accommodate them, then they've probably encountered the same thing already before, and they've come up with a way to adapt. Allowing a liberal range is like me going to France and asking for ketchup with all of my food. But having a really unusual name, like one with unmappable characters, is like me going to Riyadh and expecting them to serve booze with my meal. Should I be allowed to drink there just because it's acceptable in my culture? No. It's illegal there, and I just have to adapt whether I like it or not. Again, I emphasize, what I am advocating is for applications with a culturally homogeneous audience, not global, multicultural apps.