You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The rules seem to be focussed on US-style names. Is there any support or possibility for optional (pluggable/configurable) non-US name support?
As an example, my native tongue (Dutch) has the untranslatable concept of "Tussenvoegsel" (https://en.wikipedia.org/wiki/Tussenvoegsel), which my own name happens to use. My full name is "Martijn van der Lee", my first name being "Martijn" van last name being "Lee" with the "van der" being the third ("Tussenvoegsel") part. Having my last name as "van der Lee" (or worse "Van Der Lee") would be wrong and would cause sorting to be incorrect when used in the Netherlands.
I understand many languages (at least Irish, French, German) have similar rules for names, and it would be nice if there were a single name parser which could be configured for multiple cultures/languages or possibly even auto-detect them.
The text was updated successfully, but these errors were encountered:
The rules seem to be focussed on US-style names. Is there any support or possibility for optional (pluggable/configurable) non-US name support?
As an example, my native tongue (Dutch) has the untranslatable concept of "Tussenvoegsel" (https://en.wikipedia.org/wiki/Tussenvoegsel), which my own name happens to use. My full name is "Martijn van der Lee", my first name being "Martijn" van last name being "Lee" with the "van der" being the third ("Tussenvoegsel") part. Having my last name as "van der Lee" (or worse "Van Der Lee") would be wrong and would cause sorting to be incorrect when used in the Netherlands.
I understand many languages (at least Irish, French, German) have similar rules for names, and it would be nice if there were a single name parser which could be configured for multiple cultures/languages or possibly even auto-detect them.
The text was updated successfully, but these errors were encountered: