Bug 145530

Summary: Kphotoalbum language is not intuitive
Product: [Applications] kphotoalbum Reporter: Risto H. Kurppa <risto>
Component: generalAssignee: KPhotoAlbum Bugs <kpabugs>
Status: RESOLVED FIXED    
Severity: wishlist CC: johannes, pons
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Bug Depends on:    
Bug Blocks: 342457    

Description Risto H. Kurppa 2007-05-17 01:05:41 UTC
Version:            (using KDE KDE 3.5.6)
Installed from:    Compiled From Sources
OS:                Linux

The word 'tag' is not used at all, though it's what is used everywhere else when talking about - tagging, which is the core function of KPA.

Words like 'category', 'subcategory', 'supercategory' are not commonly used. In the 'home view' I have categories listed ('Keywords', 'Places', 'People' etc) and the next column tells me that there are 124 categories of images. OK, I've been using KPA for a while so I just ignore it, but I think a new user might not undestand the idea..

Maybe subtag and supertag  or child tag and parent tag would describe better what's going on.. I think that essentially 'keywords', 'places', 'people' are tag categories and these categories contain tags: me, my friend, helsinki, eurovision etc.. Now it's all just categories.

It's pretty difficult to translate KPA when the english terms are.. difficult to handle and understand.


So change from the massive usage of categories to tags would make the KPA language more intuitive.
Comment 1 Tim McCormack 2008-03-19 01:15:07 UTC
I like the "tag", "subtag", "supertag" language! That would indeed be more user-friendly.
Comment 2 Johannes Zarl-Zierl 2020-04-29 22:15:50 UTC
I believe this issue has mostly been fixed since your report.

KPhotoAlbum now uses the terms "category" (as listed e.g. on the home screen), "tags", and "tag groups" (for tags containing other tags).

If there are still any places where the user is confronted with confusing terms, please reopen this bug!