31 ms·
Ask HN: How to handle Asian-style “Family name first” when designing interfaces?
Our app is designed to be used across the Asia Pacific.
We have members who follow western naming conventions as well as members following common asian naming conventions.
Turns out there can be alot of variation on what is the convention.
https://www.asiamediacentre.org.nz/features/a-guide-to-using-asian-names https://www.asiamediacentre.org.nz/features/a-guide-to-using...
How would you handle different naming conventions, so users see their name in the order they would like?
Family, Given
Given, Family
- deleted 3y ago[deleted]
- foxyv 3y agoIn my opinion, name should always be a two field setup. One would be the full name for legal documentation. This can be tokenized for searching databases. The other would be the preferred name of address "You may call me Jim" which shows up on "Welcome Jim!" messages. Trying to parse out names is almost pointless. There are so many different name standards it's bonkers. If you want you could even include a phonetic section for pronunciation. If you need to split first, middle and last name for US government form entry you can just ask for those when you need them individually.
- thrwyexecbrain 3y agoIn Calibre (the ebook management software) there are two fields: "author name" and "author sort name", both free-form text. The latter serves as the sort key when the books are ordered by author. I have found this solution both elegant and practical.
- pphysch 3y agoStore "names" as a JSON document per person, and provide different view functions that construct a "full name" string based on that data and localized standards/conventions. You have infinite flexibility with nominal (heh) overhead.
- lowbloodsugar 3y agoDo other countries have a concept of a “legal” name? Like someone said their names are a set that can be in any order or just pick one: does the government insist on a single specific order for interacting with them and with, eg banks?
- contingencies 3y ago20+ years in Asia here. Have run many sites/apps and filled in many forms. Here is what you do: Full name field. (Optional) Title field. (Optional) Display name preference. (Super optional) Allow the user to duplicate ALL of these fields for EACH IANA/ISO language, eg. many people may have a Chinese or Thai name and also a separate English name with zero relation. Read https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-... and note there is an unwritten set of similar fallacies regarding signatures, plus an addresses version at https://www.mjt.me.uk/posts/falsehoods-programmers-believe-about-addresses/ https://www.mjt.me.uk/posts/falsehoods-programmers-believe-a...
- ecesena 3y agoI would call it “first” and “last” and, therefore, put “first” first. (I’m very serious, I thought a lot about this because as a non-native speaker I often get confused with expressions like “given”, “surname”, etc. don’t make me think please)
- ecesena 3y agoAnd if -by chance- you have the power of change immigration forms, I will forever be grateful.
- wageslave99 3y agoCould you put the surname with uppercase letters? That's a convention used in France that I think we should all use. In Spain, where we have two surnames (first one from father and first one from mother in either order), that would make easier for foreigners to understand that our surname is not the last word. e.g. José Luis GARCÍA LÓPEZ means García López is his surname, while José Luis is a composed name (like JFK where John Fitzgerald were his two names).
- imrehg 3y agoYou say Asian, but same order in Hungary too. Funny part, now living in Taiwan, when the forms ask me for my "English Name", I never know it means "First Last" (which would be the opposite order for me of the original form), or merely "Name in Latin characters". Names are hard.
- akasakahakada 3y agoMeanwhile Japanese company assuming everyone on this planet must have Kanji name with Katakana spelling, don't be mad at them when you can't fit your alphabet name into their scheme haha.
- joegibbs 3y agoCould you just have a single field for name and allow anything in that field? The only downside is you can't do something like "Hi ${FIRST_NAME}" in your emails, but the upside is that it basically handles any name or name order, e.g. Indonesian single names, Spanish names with the mother's surname included, etc.
- kaeresten_dit 3y agoThat's probably a good way to deal with interface issue, but do you really need their family names? It is a perhaps a good time to look at which data is needed vs what data collection from users is normalized
- hairofadog 3y agoRe: hi {first name}, I’ve had pretty good luck with a name field and then a “nickname” field that explicitly asks, “how would you like us to greet you?”
- deleted 3y ago[deleted]
- deleted 3y ago[deleted]
- masklinn 3y ago> The only downside is you can't do something like "Hi ${FIRST_NAME}" in your emails Which might be an upside, because there are cultures and contexts where it’s incredibly rude. You’re a glorified ledger, not a family member or life-long friend.
- nicbou 3y agoAnd in others the formality feels off and a tell-tale sign that the sender is not from here. I get a lot of mail from foreign readers. Indians and Pakistanis are pretty formal, and most Africans even more so. On the other hand, some people from those same countries will write stream of consciousness emails that look like a text message to their dad. The Western countries are a lot less formal, but and frequently drop the polite form which I was raised to use with all strangers.
- _darkmatterdev_ 3y agoI'm reminded of this blog post: Falsehoods Programmers Believe About Names ( https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-... ) Good luck designing your system! Sorry I don't have any advice.
- goscots 3y agoOne interesting approach would be to use a regex to detect if the name is written in Hanzi, Kanji or the Korean or Vietnamese alphabets and write the name in whatever format is appropriate for the locality. The Asian people I know would be be unsurprised to see their name rendered western style when written using whatever romanization format their native language uses.
- naniwaduni 3y agoYou can't do this: what language do you think a name like 金正恩 belongs to, and how do you rule out the others? Given this, what parts do you expect to extract from it?
- midoridensha 3y agoIt's very simple: put a drop-down field on the web form which allows the user to select which naming convention they'd like to use (generally by country, but there can be more for other regions too). This should yield only a few hundred different options to scroll through. Then each option loads a different form specific to that option. Load the whole thing in one giant blob of JS and have it load for every page view. I've seen lots of websites programmed exactly this way, so it's obviously good web design.
- kelnos 3y agoSure, but that was a direct response to someone who said "just have a single field and run it through a regex to figure things outs".
- paulmooreparks 3y agoUpvoted for the delightful use of sarcasm.
- jameshush 3y agoYou mean well so I gave you an upvote :-). I'm a Westerner living in Asia. The name my British parents gave me is James Hush. Every family member calls me Jamie. My legal Chinese name is 許杰, if you tried to write that the "Western" way the closest thing you could do is write xǔ jié, but even then there's multiple Chinese characters that represent "xǔ" and "jié" so it would make no sense. Names are hard hahahaha.
- gandalfgreybeer 3y agoPersonal opinion. As an Asian person, don’t overthink this. Just have fields for family name and given name to distinguish between the two. Sure, when there’s a text field saying hello “first name last name” it might be flipped but this shouldn’t be a deal breaker or offensive in any capacity. Worst case is you can have a toggle they can click but from a developer standpoint, that might be over engineering for something that might cause headaches later.
- evolve2k 3y agoYes assume I have a Family name field and a Given Name field, the question is how to display them in the right order. Im considering having a select field next to the name something like Name Order: "Western style", "Eastern style" or Name Order: "Given Name, Family Name", "Family name, Given Name" With a bit of extra work I can detect the country set a default for this field, while allowing users in places like Pakistan to still get the display order they want. But I've never seen it done this way before, hence my curiosity to ask everyone.
- e63f67dd-065b 3y agoAs others have mentioned, this is impossible to get right -- for the simple reason that there is no consistent order -- not for the same country, the same geographic area, the same culture, or any other marker you can possibly think of. Example: in Malaysia and Singapore, Chinese people can have traditional Chinese names -- SAA for surname and 2 characters that's their "given name" so to speak. Some have an English name -- but it's written ESAA. Some only have one character names, so it's ESA. Some surnames have 2 characters, so ESSA/ESSAA. When filling out US forms, ESAA usually turns into Englishname Surname, and SAA turns into Givenname Surname. So the display order for the first is firstlast, but the second is lastfirst. Same country, same culture, different display order depending on whether their parents gave them English names or they chose one later in life. When there's a middle name field, often ESAA names turns into E AA S - first middle last. This display order is wrong. It should be first last middle. As you can see, even within the same country, same culture, same neighbourhood, you still don't have a consistent order. It's simply not possible to do this in a consistent way.
- chomp 3y agoUse a single text field for the full name.
- djpr 3y agoThis. I'd also add "How would you like to be called" as sometimes people go by their second given name, not the first given name. For example, you might have a common first name like Muhammad or Ketut.
- wenc 3y agoI would not do this. For reasons of respect, you may need to address a person by either their first or last name (with a title). Addressing a person by their full name can come across as rude (I personally find it rude too, e.g. "Hey John R. Brown, this is your order"), so it's useful to split up "given name" and "family name" into 2 fields so that you don't have to depend on name ordering which varies by culture. If they only have one name, like many people in Myanmar, then it's just the given name. If they don't have family names (some cultures use patronymics) then it's just a long given name. If they have double-barreled last names like Hispanic names, then it's just a long family name. Most people in the world have filled out forms on U.S. sites. They'll know what to do.
- masklinn 3y ago> I would not do this. For reasons of respect, you may need to address a person by either their first or last name (with a title). Just add a field for the desired form of address, or a nickname. > Addressing a person by their full name can come across as rude Stuffy, Maybe, but rude? Calling people by their first name is rude. Calling people by forms of address which don’t exist is rude.
- davorak 3y ago> Stuffy, Maybe, but rude? Full names, at least in the USA, are sometimes used by parents to address their children when they are in trouble. Rude might not be the right word but potentially at least jarring. I have never experienced it or seen someone react that way from text but I have with verbal addresses. edit some conversations about the topic for reference since it is harder to google for than I initially thought it would be. https://www.quora.com/Why-do-parents-address-their-unruly-children-by-their-full-name https://www.quora.com/Why-do-parents-address-their-unruly-ch... https://www.reddit.com/r/AskParents/comments/pj6aqw/why_do_you_call_your_kid_by_their_full_name_when/ https://www.reddit.com/r/AskParents/comments/pj6aqw/why_do_y...
- MAGZine 3y agoHave you looked at how the tech giants before you have solved this issue?
- evolve2k 3y agoSeems many tech giants have taken a western colonial view and expect anyone different to just suck it up.
- nicbou 3y agoThe tech giants often don't account for EU customs, let alone non-Western ones. Instead I would look at how the relevant governments handle it, if they have something like the UK's component catalog.
- jasfi 3y agoYou have two fields: full name and the name you want to be addressed by (e.g. in an email). This should cover the requirements of 99% of apps. You can add another field if really needed.
- est 3y ago> the name you want to be addressed by (e.g. in an email) In fact, I don't want my full name to be addressed anywhere at all. Just call me by the alias I provided.
- jasfi 3y agoThe full name is typically used for billing, or just for record keeping. Your SaaS itself may not need it.
- vintermann 3y agoSubstitute "full name" with "legal name". Then it's the government's problem. Of course if you don't need the legal name it's best not to ask for it.
- globalise83 3y agoWon’t cover all finance apps - your name will most likely need to be submitted for sanctions screening, credit check, KYC checks etc. where understanding first name and last name is very important for cross-checking against other lists which expect the same.
- bloak 3y agoIf a message is automatically generated I'd rather it address me as "Dear Customer" or whatever. In general, perhaps it's better to have something nicely written in the manner of a circular than a badly faked personal message which is likely to impress as less human than the honest and straightforward approach. Spammers and big corporations write "Dear John, Did you know ..."; your local sports club doesn't do that crap.
- playday 3y agoIt depends on the purpose. Here you say it’s just so you can call them by their name properly, so just use a single text field “What name would you like us to address you as?”. If there’s legal or other issues that might not be good enough.
- lnxg33k1 3y agoSeems more of a stackoverflow question? But: https://github.com/kamranahmedse/design-patterns-for-humans#-strategy https://github.com/kamranahmedse/design-patterns-for-humans#... https://www.postgresql.org/docs/current/datatype-enum.html https://www.postgresql.org/docs/current/datatype-enum.html I'd have multiple classes handling each one a use-case, and a enum on user's record in order to specify which class to use for each, so that you can compute it from the nationality, but you could also potentially give each user the chance to set it for themselves
- jimbobimbo 3y agoHere's CLDR work on that: https://cldr.unicode.org/translation/miscellaneous-person-name-formats https://cldr.unicode.org/translation/miscellaneous-person-na...
- wmeddie 3y agoDefinitely read https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-... if you haven't yet. Then think about what are the requirements your system needs when it comes to names. Does the app need to know what a user's name is at all or is a username enough? Does it need to distinguish the family part of their name for anything? A thing I think is the most general is to just have a Full Name field (min length 1 and either John Doe or something cute as default) And a Nickname or Display Name field if your app needs to show something on screen.
- neoCrimeLabs 3y agoThank you for reminding me of this article! More people designing applications need to read it.
- qingcharles 3y agoAnd read this, you can learn a lot about names from it: https://studyinthestates.dhs.gov/sevis-help-hub/sevis-basics/system-data-entry-standards/name-standards https://studyinthestates.dhs.gov/sevis-help-hub/sevis-basics...
- neoCrimeLabs 3y agoThis was also educational, thank you!
- sethammons 3y ago> No hyphens, apostrophes, or commas; except in the Preferred Name field But my passport and drivers license both show my middle names hyphenated :(
- nottheengineer 3y ago> That Klingon Empire thing was a joke, right? That made me laugh out loud. It's a great reminder why being conscious of the assumptions you make is an important part of development and one that LLMs can't really do.
- hardstyle 3y agoFun fact: some cultures only have one name, i.e. no first or last name.
- qingcharles 3y agoDon't some Asians use an alternate name too, a more Westernized version of their name, alongside their native name?
- splix 3y agoNot necessary Asian btw. As a Russian I can tell that Russians also may use "family name - given name - father name", usually in official documents. Though it it also may be just "given - family", as well as any other variation informally. So you wouldn't make a mistake with UI
- ggm 3y agoIndonesia: Single name is common. Therefore only one field filled in should be legal.
- mcmoor 3y agoIt's half funny and sad that for passports one has to repeat their names for both fields or not fill the second field at all (which may be not allowed) or have to make up new name.
- ggm 3y agoYes. and for things like KYC/AML the 100 points test can get very literal about "as written on the passport"
- beojan 3y agoIn English, if the names are separated by a comma it generally indicates that they're in surname, given names order. I think this is to make sorting easier, since names are sorted in alphabetical order by surname then given names.
- deprecative 3y agoAlot of Variation is a new one. What's it look like?
- latchkey 3y agoI built an ecommerce system where we shipped hundreds of thousands of tshirts to people. They used a bazillion variations of browsers. It took a while for us to get the form 100% correct across everything. One field. Also, don't use type=number fields... the browser UX is terrible across many devices. Just make everything type=text and be done with it.
- irjustin 3y agoDon't over think it. Either: - Label the fields FAMILY, GIVEN, MIDDLE (then put them in the order you desire) - Or simply put NAME For a LOT of use cases, FULL NAME side-steps the issue and works out great. Sure your emails that go out are "Hi {{ full_name }}," but that's okay.
- wtmt 3y agoDoes your “Asia Pacific” presence include countries like India? As others have pointed out, it’s better to read that article “Falsehoods programmers believe about names” [1] and then figure out how you’d like to deal with it. Looking at “Family, Given” or “Given, Family” is shortsighted and may cover only a few east Asian countries. In India there are patronymic names with initials, mononyms (no “family name” or initials), names with just a given name (one or multiple words) and no “family name”, names where the “last name” is a place, etc. If you truly want to cater to all kinds, just have one field for name and another for what they’d like to be addressed as. [1]: https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-...
- numpad0 3y agoIf it is just for e-commerce, just steal signup form from local e-commerce websites. Or if there are local competitor platforms that does as good as yours, look into theirs. But the question sounds like there are already substantial asian users in divergent conventions without frictions. If that is what your app is trying to fix, I'm not completely sure how it will work out.
- jzwinck 3y agoI lived in Asia for many years and worked with people from many places there. It's common to hear "How should I address you?" This is equivalent to the people here suggesting a "nickname" field (good idea). There are people with only one name. Don't make them double it (Ananda Ananda). There are people with several given names. But they may only want to be called by the first, or the first two, or the last. There are people who wish to be called by their full name. They may find it jarring to be addressed by just one piece of their name. Finally there are people who go by a name which is not part of their legal name at all. Short forms like Bob instead of Robert, but also freeform names for various reasons, perhaps the most sensitive being that some government official may have determined their legal name contrary to their own wishes. Imagine your mother named you Sue but someone decided that must be short for Susan and put that on your government documents. Related: when people want to show which part of their name is the family name, they either make it all uppercase or underline it. You can see this on some CVs but it happens elsewhere too when a full name is going to be read by people who don't know the addressee.
- masklinn 3y ago> It's common to hear "How should I address you?" This is equivalent to the people here suggesting a "nickname" field (good idea). It’s not uncommon in the west either and it’s weird how much we ignored it in software e.g. “I’m John Q. Smith the Third but call me John” or “May I call you j-dog?” > There are people who wish to be called by their full name. They may find it jarring to be addressed by just one piece of their name. There’s also the issue of honorifics which you usually can’t get from names alone, as well as titles (whether professional or nobility) which can be very important to people’s identity.
- ozim 3y agoWeb apps great equalizer. No one cares if you are knighted or have phd, put in your name and you can watch funny cats same way as the rest of pleb.
- MandieD 3y agoI have an elderly German aunt by marriage who considers it an affront that Vodafone sends her chirpy business letters starting "Hallo <<first name>>!" and continuing in the familiar second person instead of the more (to her) respectful "Sehr geehrte Frau Dr. <<last name>>," and formal "Sie" (grammatically third person plural, but also the formal second person). First names and familiar second person grammar are very much reserved for family and friends in that generation. Is there a similar sentiment among older people in parts of Asia?
- saltymimir 3y agoOhh boy, as someone who works on a travel booking, service serving customers in Asia, this problem hits hard. I guess the answer depends on how you plan to handle the names once they got submitted. I happen to be handing that data over to airlines, which has some of the less forgiving, yet fragmented name requirements. If you handle this incorrectly, your customer can't fly, even after they paid for the flight. And for those who say that this doesn't matter as much: It absolutely does. People do get confused by this more frequently than you think. I've seen people losing an entire trip that they saved for, all because of unclear naming requirements. The way I deal with this is to provide a country and locale specific name fields. You don't have to detect the geolocation or track the user for this, just let them choose whatever locale setting they want, and give them the "sensible" layout. Here are some examples: - In Vietnam, we use last name then first name. - In Indonesia, we use first name, then last name, but also give an option to declare that the person doesn't have a last name. - In Singapore, we use a single field to input the first name and last name. Even when you've handled the layout convention carefully, the 3rd party you're handing the data to, if one exists, might not give the same care and attention that you do. In my case: some airlines just haven't gotten around the idea that some people simply don't have last names. When a person with a single name wants to fly, airlines want the customer to use the name for both first and last name (e.g. If the person's name is David, then the airline expects "David David"). If you require First Name and Last Name as the input, and don't elaborate on how to fill them, the customer might simply fill the last name with a dot (".") character. The airlines / any other 3rd party won't accept that. For this, I suggest to detail out the ways in which you handle the data and go talk to your providers, if any. All in all, it's a pretty tough challenge, and the wisdom around this isn't going to fit inside a single HN post. I do commend you for actually thinking about this problem. Good Luck.
- JimDabell 3y ago> In Singapore, we use a single field to input the first name and last name. I have a completely “ordinary” name from a western perspective – first (given), middle, last (family). I live in Singapore, which has a few different popular naming conventions from a few different cultures. I’ve received documents with my name in every single variation possible. I‘ve been Mr First Name, Mr Middle Name, Mr Last Name, and so on. Often I can’t even determine if they have my name correct in their records – it could be recorded correctly but used incorrectly, or it could be recorded incorrectly and used correctly. Sometimes I suspect it’s recorded incorrectly but also used incorrectly in a different way. Normally it’s not a problem, but like you say, airline tickets can cause issues. I think I’ve been demoted from “check in online” to “check in at a counter because we need to check your paperwork” a bunch of times because my passport doesn’t match my name on my ticket. Often it’s not even the name order – the airline will only sell my ticket with a first name and last name field (meaning I have to drop my middle name, which is on my passport) or they ask for all three and then concatenate first and middle with no space and truncate the last few letters. Everything would be so much easier if I could just enter my name.
- minebreaker 3y agoIMHO as a Japanese, the western convention is preferable if the app is English. It's less confusing. At least it should be consistent across the app.
- muzani 3y agoJust 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 (given name only) Malaysian name: Sharifah Azizah binti Syed Ahmad Tarmizi, (honorific surname: Sharifah) (given name: Azizah) (patronym) (father's honorific surname: Syed) (father's given name: Ahmad Tarmizi)
- eloisant 3y agoYes, basically: - one "full name" field. (English speakers would use Firstname Lastname) - one "how should we call you?" name. (English speakers would use their first name, in some other cultures people would preferred to be called by their last name)
- Fire-Dragon-DoL 3y agoWould it be better to have "full legal name" and "preferred name"? To clarify the purpose of the two
- fy20 3y agoIn most cases you don't even need the users real name. If I sign up for an account, but the invoice is going to the billing department of my company, why do you care what my real name is?
- newaccount74 3y ago> why do you care what my real name is Because the billing department verifies bills before paying them, and needs to know who to ask about the bill?
- kwhitefoot 3y agoThat's an internal matter. The supplier needs to include the customer's order number anyway or no one in the company will know how to deal with the invoice. That number will be linked to the person who raised the order.
- realusername 3y agoIt's not only and ansian thing. In France thr convention is LASTNAME Firstname (with that casing)
- froddd 3y agoI was going to say that. It’s amazing how often French users get it wrong when filling in forms. It can result in online services trying a more informal tone calling people by their last name only (“Salut, DUPONT!”), which can be seen as a bit rude. People don’t read form labels with great attention.
- CMCDragonkai 3y agoFunny in some cultures calling people by their last name is actually respectful.
- seszett 3y agoIt is respectful in France too, but only if you use a title. Say the person is DUPONT Maëlle, then: "Bonjour madame Dupont" is respectful "Bonjour Maëlle" is informal "Bonjour Dupont" is rude. "Bonjour Maëlle Dupont" or "Bonjour DUPONT Maëlle", using whatever the user put as their "name", is just neutral (though the former is less formal than the latter). Generally, you only want to address young people by their given name, and adults are more likely to find being addressed by their given name rude, than young people are to find being addressed by their family name "weird" (unless they are maybe less than 16). I find that using just the given name in any kind of official communication often has a "fellow kids" vibe.
- nicbou 3y agoIt's worth noting that this convention is also applicable in Francophone African countries, but not in Quebec.
- efitz 3y agoIs there any reason why you need to specifically know the first and last name, or the family and given name? I think there is a lot of inertia in the idea that you must have two name fields, but why? Why not just have one name field, and let people type what they want in it? Or better yet, have one field for “what should I print as the name when I send you a package or letter”, and “what would you like me to call you?” (e.g. preferred name)
- Ekaros 3y agoAlso even in west the first name + last name doesn't capture the whole effect. For example my credit card has last name, first name and middle name. And should probably be passed as such. In some addressing you want all three. But for most communication and even mailing things only first + last is enough or if more formal last + first. In the end it is huge mess with no clearly applicable rules.
- grardb 3y agoShameless plug: I gave a talk on names and the problems that arise when you give them special treatment - https://youtu.be/NfKhY3sAQ9E https://youtu.be/NfKhY3sAQ9E But the tl;dw is to do this: <input type="text" name="name" /> I don't know what kind of app you're building, but unless it's 100% impossible (from a business perspective) not to separate people's names into multiple fields, you really should just make it one field. If it's a true requirement for the business—due to a third-party vendor's requirements, for example—then I suppose you could simply ask the user which order they prefer and display their name accordingly.
- alkonaut 3y agoSo first of all everyone has read "falsehoods programmers believe about names". And of course everyone knows we should just use "name" and that's it. Perhaps a greeting/displayname if we need to do "Hello $customer" in an email. But still. There are often hard requirements that are impossible to reconcile with the "just store one name" idea. As an example: you need to produce alphabetically sorted lists. It would rarely be acceptable to produce lists of people sorted by their given names in Western Europe for example. So as an example if you really do need to have BOTH "Doe, John" and "John Doe" what do you do in case you know at least 99% of users will have names following this format? Do you force people to enter their name twice? In that situation I would: - Store it as a single name column, with more columns as required (greeting, sortable, ). - Present a UX that is appropriate for the region of 99% users. So for western Europe show a "first name", "last name", but don't store that: just set the name column to "$firstname $lastname" and the index name column to "$lastname, $firstname" and greeting to "$firstname" for example. That way I at least let 99% of your users only input the name once. - But (and this is important) offer an alternative way of specifying it for those who don't have a name that conforms to the format. You let just that small fraction of users enter a name/indexname/greeting instead. And yes: the above ONLY applies if it's really a hard requirement to separate them, because the last name sorting was really a requirement. Of course there are other requirements that force other solutions. The "just one input" is the correct solution for all the cases where it is possible.
- Hackbraten 3y ago> It would rarely be acceptable to produce lists of people sorted by their given names in Western Europe for example. Luckily, it has become a bit uncommon to manually search a printed document by name. In times of GDPR, the days of printed lists of personal info posted on some bulletin board are pretty much over. For a list that is non-public, chances are you already have it on a device with a search feature.
- nitwit005 3y agoPresenting an alphabetically sorted list only really makes sense if you can force everyone to use a single alphabet.
- ungerik 3y agovar names []string
- tommiegannert 3y agoRelated: as a Swede, the first times I had to fill out a honorific, it felt very weird. And many times they are required. We don't use honorifics in Sweden. The only difference between formal and informal address, is pretty much whether you use a nickname or not. The idea that there is a single category of "western name" is wonky. Another is that my spoken/given name is after my "middle" name. Especially American forms don't deal well with that. In Sweden, you usually underline the given name, since it's used to address the person. Now I see a comment here saying that's a thing in the Philippines. That's interesting.
- vintermann 3y agoYou used honorifics in Sweden too until fairly recently. Don't need to go further back than Pippi Longstockings (Herr Nilsson, Fröken Prysselius). And in genealogy I see plenty of Magisters, Profosses, Dragoons etc. But Swedish naming traditions are great evidence that there's no such clean divide between "western" and "eastern" naming schemes: There have actually been dialects/areas where they put the genitive form if the family/farm name first, e.g "Dals Olof" even in Swedish, and in Finnish-speaking areas this was very common.
- Findecanor 3y agoI find that while public Swedish records always store my full name, the "underlining" has often been lost. Many times I have been addressed by nurses or civil servants who assumed that my first given name was my spoken name.
- meitham 3y agoAnother case you might want to accommodate is Arabic speaking countries where the names goes like name son-of father-name son-of grandfather-name son-of great-grandfather-name tribe name. In most cases, such as when dealing with government applications four generations is required but sometimes tribe name is omitted where it can identify your religion, sect to prevent bias to you or against you. The son-of (Bin or Ibin) is mostly omitted except for cases where the first name is composite of two names, like “Mohammed Ali”, where both parts are valid names on their own.
- aaron695 3y ago[dead]
- jll29 3y agoThis is not just an Asian thing, Hungarians put their family name first (another reason not to call it a "last name"). Not to forget the special case that people may only have one name (for which some immigration offices had to invent the rule to repeat the single name twice, as first and last name, to comply with online and offline forms that have these often mandatory fields). So we may add two patterns to your pattern list: Only, Only Only Localization is tricky, not just for names, e.g. postcodes (GB) and zip codes (US) come after the city ("London SW4 0AF", "Beverly Hill, CA 90210"), in many other places before (e.g. FR, DE, e.g. "91054 Erlangen").
- devoutsalsa 3y agoI was recently in India. When using Zomato to order a food delivery, I was confused why the address form was asking for a PIN code. It took a moment to realize that PIN code was referring to what I think of as a zip/postal code.
- searchableguy 3y agoWhere did you visit in India? You liked it? :D
- devoutsalsa 3y agoJodhpur, Pune, and Agra (Red Fortress, Taj Mahal. I also went to Ellora Caves, which was amazing! India is great :)
- searchableguy 3y agoAwesome! I hope you tried all the food items including desert delicacies cooked in sand and charcoal.
- gumballindie 3y agoCommon in europe as well. Just use a name input field and a display name or preferred name field.
- wodenokoto 3y agoTry logging into Facebook with different locale settings on your Facebook account. You can have several names depending on your language. That way they can handle name order but also show English speaking contacts a readable name, while say, Japanese friends gets to see the Japanese name.
- buro9 3y agoWhat do you need their name for? Do you need their legal name? As in, actually legally need it? Realise that you'll probably need several name fields in different places depending on what you're doing, i.e. an e-commerce app may have a name to address someone by, a name on a billing address, a name on a shipping address, a name on a payment method... all of which can vary for the same person. If all you need is a way to address them, just a single name field.
- tannhaeuser 3y agoRepresenting names (and postal addressing via UPU S1) are one of the use cases where SGML/XML and other document techniques feels appropriate in internal business data representation, as opposed to storing details in 1NF (a la first/last name) in databases, especially when working with international customer data.
- cybervegan 3y agoI was wondering when someone would cite this: https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-... But since nobody else seems to have done so, I will. Globally, names don't follow any common format or concept at all that you can reduce to a formula. My takeaway is that it's best to have a free-format "full name" field, and another "preferred name" field so you can allow people to choose how to be referred to.
- gvx 3y agoHonestly, most apps don't need a full name. Just a preferred name is enough. If you really need a full name, it'll be because you need it for a specific institution, like government or bank. In that case, you probably need the ability to provide a separate full name for each institution.
- mariogintili 3y agoI18n string interpolation
- alickz 3y agoif this is an iOS app use Apples PersonNameFormatter and let the user's device localisation decide https://developer.apple.com/documentation/foundation/personnamecomponentsformatter https://developer.apple.com/documentation/foundation/personn...
- albert_e 3y agoI come from a family that traditionally writes names as Familyname Givenname. But even in our country Firstname Lastname is prevalent among many regions and central government. I grew up in the 90s and simply resigned that I will always be Givenname Familyname in most systems and documents. After school I never bothered writing / typing / filling my Familyname first anywhere. By simply staying consistent with this (wrong) way, I ensured that all my documents perfectly agree with each other. That peace of mind and lack of hassle is worth any "sacrifice" for me. Others may place different value on keeping their conventional names and must also have real reasons to do so too. I was lucky maybe, not to have those hurdles.
- ncoelhosantos 3y agoThere's an established pattern for this, which is to provide users with a choice of: Sort order: - By First Name - By Last Name Display order: - First, Last - Last, First Obviously, users can input names in a multitude of ways. But the convention is to offer at least two distinct fields, "First name" and "Last name". The sort order determines if the items are ordered by first name or last name. And the display order determines if the full name for each item is displayed as First name and then or last name, or the other way around. And finally, set a default based by the user's locale and region.
- danmur 3y agoI have nothing useful to add except that I know quite a few people who would be happy if they could have an apostrophe in their name without everything going to shit
- yakubin 3y agoAnother edge case: aside from different orderings in different countries, in Spanish speaking countries people have 2 surnames.
- smcleod 3y agoI always thought “First” and “Last” relate to the order of the names and was compatible with cultures that have self family, family self etc….?
- juliantejera 3y agoIf you have an iOS app I suggest looking into https://developer.apple.com/documentation/foundation/personnamecomponentsformatter https://developer.apple.com/documentation/foundation/personn...
- richie_adler 3y agoObRef: https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-...
- paulmooreparks 3y agoEven in England, you would have to consider King Charles III's name. His given names are Charles Philip Arthur George. No family name. Of course, now his name is even a bit longer: "Charles the Third, by the Grace of God of the United Kingdom of Great Britain and Northern Ireland and of His other Realms and Territories, King, Head of the Commonwealth, Defender of the Faith". So, if you think he might sign up for your app, make sure your name field is long enough, and that the "Preferred Name" field can accommodate a space: "Charles III" or "Charles Rex"
- deleted 3y ago[deleted]
- tectec 3y agoHe's from the house of Windsor so wouldn't he use that as his last name where it's needed?
- paulmooreparks 3y agoNo. It's not his last name. It's not even in his name anywhere. Edit: Technically, his family name is Mountbatten-Windsor. Still not a last name, though.
- rsynnott 3y agoAs others have said, there's a lot to be said for having a single name field and not trying to second-guess how people expect this to be presented. There's huge variation here, and some cultures don't even have a concept of a single last/family name.
- dv_dt 3y agoI would ask for a breakdown according cultural fields if there are interactions with external systems (e.g. payroll or banking, etc), but carry a single field preferred full name that is auto populated with a best guess suggestion.
- adulion 3y agoi work in ecommerce and we have a conditional for the order of the fields based on the delivery country the user checking out
- robobro 3y agoIn Indonesia , we have name anarchy. Some people have a family name, some people have two given names, some people only have one name, some people have many names and none of them are family names... How will your app handle people with a single name? My wife's mother splits her name in two based on syllables, but that's not exactly right. I think two fields, one mandatory -- "name" -- and other optional -- "preferred name" -- is the way to go. You should also consider how to handle people changing names, in the events of marriage, sex change, religious conversion, or what have you.
- kroltan 3y agoDon't even need to go as far as Asia, even european-descended cultures have different naming conventions. Here in Brazil, it is very common to have "compound names" which are just... two given names you have to use together, for example "Ana Maria", AND it is also common to have "middle names" which are neither family names, nor given. My name, for example, is Leonardo Giovanni Scur, but "Leonardo" is my given name that I respond and expect people to call me by, and "Scur" is the family name. "Giovanni" only exists in documents, basically. So, the first question is, what are you using their names for? If you are a paid service that identifies users to other users by name, ask for a "billing name" for your legal/policy needs, and a "display name" for identification, don't attribute any structure to it. If you don't need a legally identifying name, just ask for the "display name", and let people name themselves "Sir Bearington of Nunya Biznis".
- kroltan 3y agoTangent: A common reasoning for asking for a structured name is to build visually consistent interfaces, such as identifying everyone by their given name. But that is disrespectful to people with "complicated" names, as well as social conventions. Some people would rather be called by their family name, others their given name, and I guarantee you none of them says "but think about the pretty, homogenous UI we will be leaving behind!". For users, your brand aesthetics are at best very far down on their list of things to care about, even lower than thinking about what specific dish they will make for lunch in 3 weeks.
- Hamuko 3y agoThe name order isn't your only issue to worry about. A Japanese system might be expected to have two fields, one for the name as it's written and another for pronounciation. Just in case someone decides that 小鳥遊 as a name is pronounced as たかなし. 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.
- johnwalkr 3y agoWell there are some kanji names that have multiple pronunciations (with only one being correct for an individual). And some Chinese people in Japan go by the Japanese pronunciation of their hanzi/kanji name. They way these fields are done in Japan is often difficult if you have a non-Japanese name and give a lot of insight to this discussion. I've encountered many variations of these two sets of fields. Usually the name fields accept kanji, hiragana and katakana, sometimes accept roman letters, but sometimes if the site can be set to english, only then name fields may or must be entered in roman letters. Usually the pronunciation fields must be in katakana, but sometimes they must be hiragana and again sometimes if the site can be set to english, it may or must be entered in roman letters. Sometimes, like for a credit card application, there is a third set of fields for romanization. And for names, romanization has standard rules but there are exceptions such as when your family has been using a previous romanization so you shouldn't automate it, especially if an exact match to a passport or credit card name is required. Many other languages have different romanization possibilities for names too. There are even cases where bank insists on one romanization and the passport office insists on another leading to airplane tickets issued with the wrong one! Some (mostly old) systems require so-called full-width roman characters (same width as a Japanese character and monospace) and some systems require so-called half-width katakana. The latter usually doesn't accept small katakana or diacritical marks, making it difficult to read and write non-Japanese names (or company names for that matter). Back in the day to transfer money at a bank you had to successfully write the recipient's name this way but these days all banks can automatically grab the katakana name and you just have to check it (but it's still in hard to read half-width katakana). A common annoyance is when everything must be in full-width characters except phone number which must not be. Finally, there is one type of field that really can trip you up: the address field. It usually must be in full-width characters which is fine in principle, but building names are often (officially, on the record) in English. The windows Japanese IME will happily default to "normal" and not full-width characters. This is easy to spot for a building name and figure out your mistake. But if you live on the third floor (denoted by adding "-3F") it's hard to spot an accidental "-3F", "-3F", "-3F" or especially "-3F" (the dash is wrong).
- SeanLuke 3y agoWait until you see Icelandic names where there is no last name at all. Björk's "last name" is Guðmundsdóttir, because she is the daughter of Guðmundur, whose "last name" is Gunnarsson, because he is the son of... The 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.
- registeredcorn 3y agoThere's an excellent GitHub repo that lists a lot of common falsehoods regarding names. I'm not sure how useful it'll be to OP, but the repo in general should probably have way more attention than it already does. https://github.com/kdeldycke/awesome-falsehood#human-identity https://github.com/kdeldycke/awesome-falsehood#human-identit...
- IlliOnato 3y agoAfter reading that document and the comment section, it seems that the really distinct name variants are: 1. Full legal name (as it appears in a passport, e.g. William Robert Smith) 2. Full formal name (this is how you want to be addressed and/or referred in a formal context, e.g. Dr. Professor William R. Smith, MP". 3. Abbreviated formal name (e.g. W. R. Smith) 4. Informal name (how you want to be referred/addressed in less formal context, e.g. Bill Smith) 5. Highly informal name (how you want to be addressed in close circles, e.g. Bill) 6. Nickname (e.g. Chuck) It seems that (more or less European) convention of having first name(s) and a last/family seems have this goal: being able to store just one variant and to generate other variants (except the nickname) according to fixed rules, in other words, automatically. Of course you should ask a user only of what you need. So if the only reason you ask for a name is to be able to address them in messages, you should ask "how you would like me to call you?" or something like this. You can give users an option to, say a check box, to indicate their names follow the "European" convention, and then give them the fields that allow to auto-generate name variants, allowing them to override if necessary. Just my 2 cents :-)
- mrcgnc 3y agoOther things I've had to deal with: in Myanmar people usually don't have a concept of first and last name, just two (females) or three (males) words that form their "name" (as far as I can remember). Also, often names in Sri Lanka look like this: Rajapaksha Mudiyanselage Siril Ariyaratna. Two family names and one or two given names. Regardless of the number of fields used, displaying long names like that needs some special considerations.
- Larrikin 3y agoIn the Android apps I've worked on, family name and given name are saved separately in the database and then in our string file we have a separately defined string "full name format" that just takes in two strings. Depending on the localization string file, the two strings can be reversed. Haven't had to do major internationalization efforts in many apps I've worked on but this has been perfectly fine for times we needed to have multiple formats. Just considering other countries and languages (and not doing obviously American/English only) has made the effort considerably easier, even when other countries aren't in the radar at the time
- wirthjason 3y agoOn the flip side, I wish rat Japanese design allowed for middle names. It annoys me that my marriage certificate has my first and middle name concatenated together simply because my legal name on my passport has a first, middle, and last name.
- alentred 3y agoNot suggesting it for the UX, more of a curiosity: in France, a somewhat common convention is to put the family name in uppercase. This is well known by everyone, but not everyone does that. Sometimes you would receive an email from "Robert Martin" and stop for a second to figure it out.