6 ms·
Whenever I'm on a team building something new, I've fought hard to stop people from splitting names into first/last. There's simply no right way to do it. In ad
by caymanjim 7y ago
Whenever I'm on a team building something new, I've fought hard to stop people from splitting names into first/last. There's simply no right way to do it. In addition to conventions like family name first in Japan, Spanish naming conventions create confusion (First Paternal_Family Maternal_Family), and there are rare outliers like mononyms as well. There is almost no use case--aside from perhaps a genealogy site--where splitting the name provides any benefit.
- favorited 7y agoInteresting! I wouldn't have thought that would be best practice, but in spending a little time trying to learn more (this page from W3[0] was really enlightening), it makes perfect sense why "only split if you absolutely need to" is good advice. [0]https://www.w3.org/International/questions/qa-personal-names https://www.w3.org/International/questions/qa-personal-names
- aikinai 7y agoWhat about sorting, reordering (as in the article), or allowing the user to pick preferred order? Also allowing other data such as phonetic name to be applied per name (again useful for sorting and other features). There are tons of reasons to split names and I’m just a basic user of contacts apps. This all comes to mind immediately since Apple splits names and Google doesn’t, making Apple products much more useful and elegant with Japanese names.