[ChrisMarshallNY]

East Asian names (Korean, Chinese, Japanese, etc.) can have a great deal of variation in surname/given name positioning.

In my app, I don't even try to separate them. I just give a single string that can handle UTF-8, and let the user do what they want.

However, I also don't need that data for tagging, sorting or anything else, so it's easy for me to say.

[loloquwowndueo]

I’ve been in this boat and then had to justify the choice when integrating with third party vendors whose backends absolutely want names split into first/last components.

We would set up integrations sending the full name in the “first name field” and then a hard coded “notmylastname” string in the “last name field”. And then have about 3 days of back and forth usually including a link to https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-... and explaining that no, you can’t reliably use a regular expression to split the full name data into first/last components.