Bug 293717 - Inconsistent description categories vs. tag
Summary: Inconsistent description categories vs. tag
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kaddressbook
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR minor
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-09 14:41 UTC by Michael Skiba
Modified: 2017-01-07 22:22 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Skiba 2012-02-09 14:41:47 UTC 
Version:           unspecified (using KDE 4.8.0) 
OS:                Linux

This is a problem introduced through nepomuk I guess:
While the "vCard-View" (where you edit the personal details of your contact) says "Categories: ___ ...", when you click on the button behind the label to actually add a category it says Tag (which is the nepomuk default)

Actually this is not a problem for me and is at best a cosmetic problem I just wanted to mention it, since I stumbled upon it.

Reproducible: Always

Steps to Reproduce:
Cosmetic bug - no additional details

Actual Results:  
Cosmetic bug - no additional details

Expected Results:  
Cosmetic bug - no additional details

Cosmetic bug - no additional details
Comment 1 Michael Skiba 2012-02-09 14:46:14 UTC 
For a screenshot of the German version you can see https://bugs.kde.org/show_bug.cgi?id=293715 (The German translation correlates exactly to the English one)
Comment 2 Denis Kurz 2016-09-24 20:52:32 UTC 
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kaddressbook (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 3 Denis Kurz 2017-01-07 22:22:53 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.