Bug 88384 - No Formated Name in Table view
Summary: No Formated Name in Table view
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kab3
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: RedHat Enterprise Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Tobias Koenig
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-29 15:35 UTC by Avi Alkalay
Modified: 2009-08-05 16:14 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Avi Alkalay 2004-08-29 15:35:16 UTC
Version:           3.3.0 (using KDE KDE 3.3.0)
Installed from:    RedHat RPMs
OS:                Linux

I synced from my Palm, and by default kpilot does not create the "FN:" field in address entries.

Then KAddressBook does not automatically calculate them in Table View mode.
It does autocalculate in Card or Icons View mode.
Comment 1 Tobias Koenig 2004-08-29 17:22:17 UTC
On Sun, Aug 29, 2004 at 01:35:17PM -0000, Avi Alkalay wrote:
Hi Avi,

> I synced from my Palm, and by default kpilot does not create
> the "FN:" field in address entries.
> 
> Then KAddressBook does not automatically calculate them in Table View mode.
Of course not, because the formatted name has to be set explicitely by
the user, that's the meaning of this field.

> It does autocalculate in Card or Icons View mode.
No, they doesn't use the formatted name field for displaying, since the
formatted field could be empty, and a icon or card without a title looks
quite strange ;)

In the table view instead, you can have several other columns, so an
empty formatted name field doesn't matter much.

Ciao,
Tobias
Comment 2 Avi Alkalay 2004-08-29 17:45:16 UTC
OK, so from my point of view, this is a usability issue.
I personally think that to have too columns is a waste of space and not very clear for human eyes and brains. Any other address book tools I've been using (e.g. the Windows Palm Desktop) joins them in one field.

Besides, it is not exactly explicitly set. If you simply set a name and last name, FN is automatically set. Or if you open the contact (that doesn't have a FN set) dialog, you can already see a formated name already (automatically) there, but on the table view its still not there.

I still think this is something that must be tunned, for usability.
Or at least add a special column option as "joined name and last name".

Again, this is something that happens only when you import from Palm. If you create a contact by hand, FN will be automatically calculated, as it should be.
Comment 3 Tobias Koenig 2004-08-29 19:34:55 UTC
On Sun, Aug 29, 2004 at 03:45:19PM -0000, Avi Alkalay wrote:
Hi Avi,

> OK, so from my point of view, this is a usability issue.
> I personally think that to have too columns is a waste of space
> and not very clear for human eyes and brains.
Yeah, so use just the formatted name field and tell your pilot tool to
create the formatted name. That's not a usability issue in KAddressBook
but a wrong handling.

> Any other address book tools I've been using (e.g. the Windows Palm Desktop)
> joins them in one field.
Well, then they don't follow any specification... read RFC2426 for the
purpose of the formatted name field.

> Or at least add a special column option as "joined name and last name".
That's the same like formatted name...

> Again, this is something that happens only when you import from Palm.
> If you create a contact by hand, FN will be automatically calculated, as it should be.
So it's a problem of the tool you are using for importing your contacts
from the Palm

Ciao,
Tobias
Comment 4 Artur Frycze 2005-06-17 13:44:22 UTC
I synchronized contacts with Nokia 6600 - ALONsoft ContactGuide application exports vcards without FN field.
so i got hundreds of blank contacts.

i think that FN should be auto-generated if no FN exists.
Comment 5 Tobias Koenig 2009-08-05 16:14:04 UTC
The development of the old KAddressBook will be discontinued for KDE 4.4.
Since the new application has the same name, but a completly new code base we close all bug reports against the old version and ask the submitters to resend there reports against the new product.