contacts
contacts copied to clipboard
Distinction between first and last name
We should definitely try to do this in the backend. It’s already painful to need to put in the address in 5 or 6 different fields (everyone HATES forms) so we definitely should not have separate input fields for the name. The old Contacts app didn’t have it either, at least not by default.
cc @tanghus @jbtbnl @babelouest if you feel like contributing again. :)
Name editing in the old contacts app
editing addresses in old contacts app
Damn … then it was probably wishful thinking, or it of course works like that on Android etc. ;)
In Android I think the contact app split automatically the Name you enter and divide the data into the FN field.
Example, if you type "John Doe", it will set John as first name and Doe as last name. Maybe we should do that with a div expand possibility to correct the FN fields?
Currently new Contact only have FN-Value (Displayname) and N-Value (Full Name with Family Name, Given Name, Additional Names, Honorific Prefixes, and Honorific Suffixes as in RFC 2426) is not editable.
A lot of progams use algorithms to split names (eg. Outlook, Android, iOS), but none works perfectly. there are too much ways to write a full name....
related to #276 ??
@ionum Somehow we already have an algorithm: "do nothing". Which is really annoying when using any other contact application. Personally I would prefer the 8.1 contacts behaviour:
- Show only a single input field and try to split the input to first name and given name with an algorithm
- Give the user the possibility to display and edit the name detail fields, if he needs to correct the result of the algorithm
@XZS1cpXn yes, sure. Just for clarification, the reason for this is that it's a completely new app which replaced the old one. Since unfortunately resources are scarce, some things are not done yet. :)
Moreover, i think it could help with contact sorting (issue #208).
my first try #418
might be relevant: https://github.com/joshfraser/JavaScript-Name-Parser
That libs dead Baby, that libs dead! Last commit 2 years old
:skull: Nooooooooo
Shouldn't this issue be fixed with #437?
@phsc yup, thanks!
We can do enhancements in the future, but for now this should fix it.
Or wait – this was for the other issue.
This issue is about parsing the name, which is an entirely different beast. ;)