3 ms·
I’m trying to figure out what the issue is here. The Spanish example given isn’t even a real problem: even Spanish speaking countries only use two columns (“fir
by someotherperson 3y ago
I’m trying to figure out what the issue is here. The Spanish example given isn’t even a real problem: even Spanish speaking countries only use two columns (“first names” and “last names” plural). It really feels like it’s trying to invent a problem that doesn’t exist, or to try to cater for the extreme edge case.
Once you have the data, how you present it as a separate i18n thing. Do you want to address an <ethnicity> crowd by their last name? Cool! That’s a rendering issue, not a database problem.
- agubelu 3y agoI understand that the author's point is that we should replace "first name" with "given name(s)" and "last name" with "family name(s)" if we are going to have two fields instead of just one for the full name. It's true that it would be more clear in some cases, since in many cultures the "first name" is the family name, which is probably not what the system expects. Though I do agree that it's mostly a matter of i18n. In Spanish you should ask for "nombre" (name) and "apellido(s)" (surname), if you say "given name" and "family name" users will be confused.
- hunter2_ 3y agoIdeally it would just ask for each actual need. If the system needs to render something brief for a salutation, something verbose for a certificate of achievement, and something suitable for sorting purposes, then it could just ask the user to provide all of those exact things. Then the potential for misalignment with "what the system expects" completely disappears.