summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRodney Dawes <dobey.pwns@gmail.com>2008-08-29 17:59:56 +0000
committerRodney Dawes <dobey.pwns@gmail.com>2008-08-29 17:59:56 +0000
commitd2ea8b37fde638d66a8282ebb14c87cb6903350a (patch)
treec1f2d4092fc27111df20e9113e903de918ca7f75
parentac5c48fd45ad3a17e1f26fe410a325c75b74b533 (diff)
Expand note on naming application icons to state the standard fallback method
should not be used for the Applications context
-rw-r--r--spec/icon-naming-spec.xml14
1 files changed, 9 insertions, 5 deletions
diff --git a/spec/icon-naming-spec.xml b/spec/icon-naming-spec.xml
index a791071..84ce033 100644
--- a/spec/icon-naming-spec.xml
+++ b/spec/icon-naming-spec.xml
@@ -205,11 +205,15 @@ for a USB mouse device. However, if the more specific item does not exist
in the current theme, and does exist in a parent theme, the generic icon
from the current theme is preferred, in order to keep consistent style.
</para>
- </listitem>
- <listitem>
- <para>
-Icons for branded applications should be named the same as the binary
-executable for the application.
+ <para>
+The <quote>Applications</quote> context should not use this method of
+falling back to more generic icons. An application must either use a
+generic application icon name provided by this specification, or install
+an icon named the same as the executable for running the application. A
+generic desktop application included with the desktop suite, such as the
+calculator or terminal application, should use the generic names provided
+by this specification, as described above in the <quote>Applications</quote>
+context description.
</para>
</listitem>
</itemizedlist>