I remember Amazon.co.jp having two name fields when you registered a new user, and in English they were called "Your name" and "Your name again", because a name pronounciation field probably makes little sense as a concept to most non-Japanese speakers.
Ask HN: How to handle Asian-style “Family name first” when designing interfaces?
341–350 of 527 posts
Re: Ask HN: How to handle Asian-style “Family name first” when designing interfaces?
#342Earlier quoted context omitted.
The GOV.UK design system[1] agrees with you: > "Use single or multiple fields depending on your user’s needs. Not everyone’s name fits the first-name, last-name format. Using multiple name fields mean there’s more risk that a person’s name will not fit the format you’ve chosen and that it is entered incorrectly." and > "Avoid asking users for their title. It’s extra work for them and you’re asking them to potentially…
>> "Avoid asking users for their title. It’s extra work for them and you’re asking them to potentially reveal their gender and marital status, which they may not want to do." I'm always a bit surprised when I see some e.g. tech conferences still insisting on title as a mandatory field (or really asking at all). It's not just the gender and the marital status but some people attach a lot of significance to all manner…
Re: Ask HN: How to handle Asian-style “Family name first” when designing interfaces?
#343Earlier quoted context omitted.
Sorting. Though I don't think there's a culture-agnostic way to do this, either.
Not universally, no. The closest for English-language use is to put a spurious comma between family and given name (e.g., "Cixin, Liu" for Cixin Liu). In an ebook management system I've been developing, I use a full_name and a sort_name field for authors/editors/contributors, because books are a reasonable thing to want to sort by author names.
Re: Ask HN: How to handle Asian-style “Family name first” when designing interfaces?
#344Earlier quoted context omitted.
"Just have a single "name field" and maybe preferred name, which is not the same." This is the way to go. "The family/given name format doesn't make much sense here." It doesn't make much sense in many places all over the world. In Germany technically speaking our given names are a set and we can have many of them. While it is practically necessary to write them out in a certain order in our documents, from a legal s…
> "Just have a single "name field" and maybe preferred name, which is not the same." > This is the way to go. Agreed. Does anyone know of any reason to care about first/last, apart from it being part of My First SQL Database and sating our inner desire to create pointless taxonomies?
Re: Ask HN: How to handle Asian-style “Family name first” when designing interfaces?
#345Earlier quoted context omitted.
Sorting. Though I don't think there's a culture-agnostic way to do this, either.
Not universally, no. The closest for English-language use is to put a spurious comma between family and given name (e.g., "Cixin, Liu" for Cixin Liu). In an ebook management system I've been developing, I use a full_name and a sort_name field for authors/editors/contributors, because books are a reasonable thing to want to sort by author names.
For example, in my studies I had cause to read many books by Hans Urs von Balthasar. Nobody ever referred to him as "von Balthasar," just "Balthasar," but his books were always sorted by the "von."
Re: Ask HN: How to handle Asian-style “Family name first” when designing interfaces?
#346Just have a single "name field" and maybe preferred name, which is not the same. The family/given name format doesn't make much sense here. Indian name: Sathiavelllu Arunachalam, known as SA or Seth SE Asian ethnic Chinese names: Harry Lee Kuan Yew, (English name) (Surname) (Given name). Hated the name Harry and got it removed, though many Chinese are referred to by an English name. Indonesian name: Fatimah Azzahra (…
And don't forget people with just a single name. Filling in computer forms that require two names is the bane of my existence.
I would also mention that I feel your pain to a degree. My wife has an extremely uncommon female name, but the spelling is very close to a common male name. Many times she has run into people "fixing" her name for her without saying anything only for it to cause issues months later, or people calling her by the name they assumed she meant to type. It's incredibly aggravating to deal with. Lots of missed emails. Lots of phone calls of helpful people informing her of the "error".
At times, I wish the entire naming system were replaced with something that had no room for error or miscommunication. Everyone is called Larry or something.
Re: Ask HN: How to handle Asian-style “Family name first” when designing interfaces?
#347Just have a single "name field" and maybe preferred name, which is not the same. The family/given name format doesn't make much sense here. Indian name: Sathiavelllu Arunachalam, known as SA or Seth SE Asian ethnic Chinese names: Harry Lee Kuan Yew, (English name) (Surname) (Given name). Hated the name Harry and got it removed, though many Chinese are referred to by an English name. Indonesian name: Fatimah Azzahra (…
The GOV.UK design system[1] agrees with you: > "Use single or multiple fields depending on your user’s needs. Not everyone’s name fits the first-name, last-name format. Using multiple name fields mean there’s more risk that a person’s name will not fit the format you’ve chosen and that it is entered incorrectly." and > "Avoid asking users for their title. It’s extra work for them and you’re asking them to potentially…
https://www.gov.uk/government/publications/titles-included-i...
My personal favourite is if you change your first name to “Sir” and you are not actually a “Knight”, then you get the note “THE REFERENCE TO SIR IS TO THE HOLDER’S NAME AND NOT TO THE HOLDER’S TITLE” printed in your passport.
Context: I wanted “Dr.” to be added to my passport.
Re: Ask HN: How to handle Asian-style “Family name first” when designing interfaces?
#348Earlier quoted context omitted.
The GOV.UK design system[1] agrees with you: > "Use single or multiple fields depending on your user’s needs. Not everyone’s name fits the first-name, last-name format. Using multiple name fields mean there’s more risk that a person’s name will not fit the format you’ve chosen and that it is entered incorrectly." and > "Avoid asking users for their title. It’s extra work for them and you’re asking them to potentially…
Title is the one that always confuses me since titles are basically non-existent here. It seems really like a really important thing in the Anglosphere and I have no idea why. I just always pick "Dr" when I'm forced to pick one. So far it has never made any difference.
Re: Ask HN: How to handle Asian-style “Family name first” when designing interfaces?
#349Earlier quoted context omitted.
The GOV.UK design system[1] agrees with you: > "Use single or multiple fields depending on your user’s needs. Not everyone’s name fits the first-name, last-name format. Using multiple name fields mean there’s more risk that a person’s name will not fit the format you’ve chosen and that it is entered incorrectly." and > "Avoid asking users for their title. It’s extra work for them and you’re asking them to potentially…
Title is the one that always confuses me since titles are basically non-existent here. It seems really like a really important thing in the Anglosphere and I have no idea why. I just always pick "Dr" when I'm forced to pick one. So far it has never made any difference.
Re: Ask HN: How to handle Asian-style “Family name first” when designing interfaces?
#350The Indian name situation, going by initials instead, is particularly interesting. There is a famous professor I know who goes by initials because his second name is forty letters long.