[Rtcomm] [Rtcomm] [Bug 6704] Contacts doesnt automatically extrapolate first and last name

[From: bugzilla-daemon at maemo.org]

https://bugs.maemo.org/show_bug.cgi?id=6704





------- Comment #5 from bugzilla770 at nmacleod.com  2009-12-15 15:33 GMT+3 -------
To be honest, I thought this was a no brainer. Basing the reason not to
implement a workable solution on a blog posting by someone I've never heard of
is hardly valid justification, is it?

Nobody is suggesting that name parsing can be implemented 100% perfectly, but a
large number of "contact" names *could* be parsed correctly most of the time
which is surely better than none of the time, as we have now.

I totally understand there will be exceptions to this rule, but why make life
difficult for all users simply because it isn't possible to be perfect? You're
going to annoy the users anyway because the import process makes no effort to
get the names right so at least assisting those who can benefit from a bit of
parsing seems a positive move.

When faced with importing, say, 100 contacts with a large percentage in
"firstname lastname" format (and the remainder in some odd variation) would you
rather the import process gets them all wrong (ie. dumps the whole name in a
single field, as it does now) or have it correctly import the majority leaving
you to fix up just the minority of contacts that couldn't be parsed correctly?

Please consider offering the option to "Import and infer firstname / lastname"
from the data as an option during the import process, or you could even go so
far (maybe too far!) and infer these fields automatically whenever there are no
distinct firstname / lastname fields present in the data to be imported.

Doing something positive rather than nothing at all seems a no brainer to me.


-- 
Configure bugmail: https://bugs.maemo.org/userprefs.cgi?tab=email
Replies to this email are NOT read, instead please add comments at
https://bugs.maemo.org/show_bug.cgi?id=6704
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.