2 ms·
Okay but say a person with an East Asian name fills out your form and dutifully fills out your form with their name in reverse. i.e. if their name is the Chines
by zarzavat 3y ago
Okay but say a person with an East Asian name fills out your form and dutifully fills out your form with their name in reverse. i.e. if their name is the Chinese equivalent of “Smith John”, they fill it out as given name: John, family name: Smith. Aren’t you going to be rendering their name in the wrong order for all your interactions? How do you know which order to concatenate it?
- manfre 3y agoThis is why you'd use the single "what do you want to be called?" value (e.g. preferred_name). Then it's not an issue because it's the exact text they provided.
- dgoldstein0 3y agoI think the point is it's a single field so you don't do any concatenation
- marcus_holmes 3y agoThis. There's two separate concerns: what you call them, and their "official" name. What you call them is always better done as a separate single field, rather than trying to concatenate the official name fields.
- numpad0 3y agoYou're mixing up multiple problems. If adding problems is what you want, none of my highschool classmates called each others in the "John" part of anyone's names, and emails beginning with a "Hello $firstname" in my language sounds weird to me anyway. But first/last names are often reused for billing and official purposes, so East Asian(CJK) users would know to fill the "first" with given and "last" with family name if asked that way for official purposes, no matter the visual order or how will it be used. If it's not for official purposes, people are just going to throw in random junks anyway.