according to vCard 3.0 RFC at https://tools.ietf.org/html/rfc2426#section-3.1.2
Type name: N
Type special note: ... The property MUST be present in the vCard object.
The problem with the FN attribute is that you usually have an interface where you can
choose the order of columns (e.g. First, Last) and also the sorting of columns (e.g. Last,
First). In this case the information in FN is completely useless because you don't
know which part of FN is the last and which is the first name.
So InfCloud completely ignores the content of FN, but when you create a new (or edit an
old) contact if fills the FN according to settings in config.js for older clients ...
there is clearly no "good" solution if someone ignores the RFC.
On 20 Dec 2019, at 09:50, Johan Vromans
When a contact is synced in that has an FN field but no N field, the entry
in InfCloud becomes nameless. The contents of the FN seems to be ignored
Would it be possible (feasible, acceptable, allowed) to infer name fields