Hi,

Here's a small patch fixing really minor stuff in the desktop entry
spec:

 + fix typos
 + remove duplicate description of what can be in a group header
 + move some text around
 + fix value type for the Icon key

I'd like to update the spec a bit more, so we can at least make 1.0
nearer :-) Here are some things I'd like to do (I hope they all make
sense):

 + reorganize the text, so that we really have the basic format first,
   and not described all over the spec

 + move all of the "Legacy-Mixed encoding"-related stuff in appendix D
   and move it from "MUST be supported" to "MAY be supported". The glib
   API to parse .desktop-like files does not support this, and I don't
   think it's planned. This would also imply deprecating the Encoding
   key.

 + is the FSDevice type used by a project? We don't use it in GNOME, and
   I'd like to deprecate it if possible.

 + see if all keys are useful. I'm not sure SwallowTitle or SwallowExec
   are used, eg. And SortOrder. It's also not clear to me why we need
   FilePattern if we have TryExec.

 + I wonder about the Actions key. It does make sense to me, but we
   don't support it in GNOME and we only had one (old) bug report about
   it. Do other projects use it?

 + fix all the ambiguous parts. For example, what type of regexps are we
   supporting?

I'll send patches for those things later if there's consensus about
them.

Thanks,

Vincent

-- 
Les gens heureux ne sont pas pressés.
? issue
Index: desktop-entry-spec.xml
===================================================================
RCS file: /cvs/menus/desktop-entry-spec/desktop-entry-spec.xml,v
retrieving revision 1.9
diff -u -p -r1.9 desktop-entry-spec.xml
--- desktop-entry-spec.xml	13 Jul 2004 22:05:05 -0000	1.9
+++ desktop-entry-spec.xml	22 Apr 2006 07:58:56 -0000
@@ -68,15 +68,11 @@
       be other groups present in the file, but this is the most
       important group which explicitly needs to be supported.  This
       group should also be used as the "magic key" for automatic MIME
-      type detection.  There should be nothing proceeding this group in
+      type detection.  There should be nothing preceding this group in
       the desktop entry file but possibly one or more comments (see
       below).
     </para>
     <para>
-      Group headers may not contain the characters <literal>[</literal> and
-      <literal>]</literal> as those delimit the header.
-    </para>
-    <para>
       Lines beginning with a <literal>#</literal> and blank lines are
       considered comments and will be ignored, however they should be
       preserved across reads and writes of the desktop entry file.
@@ -97,6 +93,11 @@
       sign is the actual delimiter.
     </para>
     <para>
+      Case is significant.  The keys <varname>Name</varname> and <varname>NAME</varname> are not equivalent.
+      The same holds for group names.  Key values are case sensitive as
+      well.
+    </para>
+    <para>
       The escape sequences <literal>\s</literal>, <literal>\n</literal>,
       <literal>\t</literal>, <literal>\r</literal>, and
       <literal>\\</literal> are supported, meaning ASCII space, newline,
@@ -237,12 +238,7 @@
       then the value of the <varname>Name</varname> keyed by <literal>sr_YU</literal> is used.
     </para>
     <para>
-      Case is significant.  The keys <varname>Name</varname> and <varname>NAME</varname> are not equivalent.
-      The same holds for group names.  Key values are case sensitive as
-      well.
-    </para>
-    <para>
-      Keys are either OPTIONAL or REQUIRED.  If a key is optional it may or
+      Keys are either OPTIONAL or REQUIRED.  If a key is OPTIONAL it may or
       may not be present in the file.  However, if it isn't, the
       implementation of the standard should not blow up, it must provide
       some sane defaults.  Additionally, keys either MUST or MAY be
@@ -361,10 +357,9 @@
           name is an absolute path, the given file will be
           used. If the name is not an absolute path, an
           implementation-dependent search algorithm will be used
-          to locate the icon. Icons may be localized with the
-          <literal>Icon[xx]=</literal> syntax.
+          to locate the icon.
 	    </entry>
-	    <entry>string</entry>
+	    <entry>localestring</entry>
 	    <entry>NO</entry>
 	    <entry>YES</entry>
 		<entry>1-4</entry>
@@ -474,7 +469,7 @@
 	    <entry>
            The MIME type(s) supported by this entry.
 	    </entry>
-	    <entry>strings(s)</entry>
+	    <entry>string(s)</entry>
 	    <entry>NO</entry>
 	    <entry>NO</entry>
 		<entry>1</entry>
@@ -741,7 +736,7 @@
 	    </entry>
 	  </row>
 	  <row>
-	    <entry>%i</entry>
+	    <entry><literal>%i</literal></entry>
 	    <entry>
               The <varname>Icon</varname> field of the desktop entry
               expanded as two parameters, first
_______________________________________________
xdg mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/xdg

Reply via email to