4 ms·
This is not sufficient if you’re going to localize to languages other than English. In some languages, proper names get declined like other nouns and thus chan
by kd5bjo 7y ago
This is not sufficient if you’re going to localize to languages other than English. In some languages, proper names get declined like other nouns and thus change spelling in different contexts.
- deleted 7y ago[deleted]
- detaro 7y agoAre there examples where splitting it in First/Last name (or any other split) would help with that? It seems like that would always either be a problem or something to design around while localizing.
- kd5bjo 7y agoIt’s fundamentally language specific, so any comprehensive solution is going to need to interface with the localization system. Really, names should be keyed by (user, language, tag) triples, where the localization defines the acceptable tags based on language requirements. For example, a single person may need their name stored as: en:disp Eric is:disp:nf Eiríkur is:disp:þf Eirík is:disp:þgf Eiríki is:disp:ef Eiríks Designing a UI to collect this information is left as an exercise for the reader.
- dkersten 7y agoSince asking a user to enter every possible variant is unwieldy and without doing so, the problem is unsolvable, I’ll stick with my original suggestion of using a single field. Yes, some names will break, but far fewer than if first and last names are required.