Talk:Projects/Oxygen/namingSpec/apps

Specification compliance of icon names

I think that things under this heading should deal with compliance with the FD.o Icon Naming Spec.

The list of KDE ONLY application names has nothing to do with this since all branded names are automatically in compliance. I agree that the menu icon for an application should be installed by the application. With KDE apps that come ONLY in the KDE packages, this can be done by the package rather than the individual apps.

It is also true that branded icons for other applications are also automatically in compliance with the spec.

In either case, I see no purpose that is served by listing these here.

The issue of where to install them should be addressed on: <[email protected]>

--JRT 22:53, 25 July 2007 (CEST)

Specific icons

krbf

Currently KDE3 uses this in the Control Center. The proper name for this icon would be: "preferences-desktop-remote-desktop" (Tango name). Therefore, this icon can not be moved to the application. It can, if needed be copied to the application or the application can simply use the spec type name.

--JRT 23:26, 25 July 2007 (CEST)

Icons for non-KDE applications

x: This seems to be 'Duh!'. It is used for X utilities that don't have a specific icon and should therefore be named: "utilities-x". Icons for specific X utilities will add on to this base name.

acroread: This is a different case. Adobe provides an icon for this named: "AdobeReader". This violates the spec because it isn't all lower case. Also, this application belongs to a class and there is the question of fall back.

--JRT 01:13, 26 July 2007 (CEST)

Icons for KDE applications which belong to a class

For example: "kpdf" is a member of the class: "PDF viewers". The Adobe Acrobat Reader also belongs to this class.

Should such KDE app iconss be named so that fallback works?

--JRT 01:17, 26 July 2007 (CEST)