I think instead of trying to break names apart from one input, the best strategy is to consider the various uses you need and provide that many inputs (in a pre

I think instead of trying to break names apart from one input, the best strategy is to consider the various uses you need and provide that many inputs (in a previous job writing software for art galleries, this was our solution). So for example, you might have a "display name" field, which is the formal name-of-record that you need for any official or semi-official context (title card of an artwork, or invoice info, going on the art example). For indexing/sorting, you can have that as a separate "index" or "sort value" field (especially where sorting is something you want to control on a per-entry basis, like the library example in one of the articles sorting names using the indexing rule of the author's place of origin, or you want to sort a list of names that contain a mix of character sets). For addressing people directly, e.g. via email or letter, you can provide them with an extra "how should we address you" field -- the best part about this is it means you don't have to guess how they want to be addressed, and is I think the most polite option, especially when you're dealing with a variety of cultural contexts in the same system.