answered
2013-12-26 12:00:12 +0200
Yes, this is a known limitation. The data received from the facebook-chat IM roster does not provide any breakdown of the name tokens - we just receive a single datum: 'Peter de Jong'. Those three tokens are then allocated according to a rule for the phone's locale, which will most likely see them allocated as 'firstname', 'middlename', 'lastname'. So the surname prefix token will have been applied as a middle name.
We considered adding a list of common tokens that would be processed as prefixes to a surname, such as 'van', 'de', 'van't', 'van de', 'van der' and so forth, but since we wouldn't know the origin of the incoming name, we could only apply rules to the name from the phone's locale. Any case where a token was misallocated to the surname would be considerably more confusing and difficult to locate than one where the prefix was lost from the surname.
Any alternative suggestions appreciated...
I think this question would better gather all the attention it needs, if it was rephrased something more like
Contacts in the People app are treated incorrect, when the persons last name consists of more than one string-of-text, either due to the last name having one or more particles, or the full last name consisting of more than one name (with or without hyphens).
and not be limited to Facebook contacts.
similar question
@darius' "Wrong Names and Surenames on People app."
but also
phle ( 2014-02-11 13:58:50 +0200 )edit@jonathanarcher's "Bug: Unable to add contact with name similar to existing one"