Current desktop file spec unclear on validity of non-set Path entry
Submitted by Jonathan Thomas
Assigned to Allison Lortie
Currently the fd.o spec regarding .desktop files is unclear about whether or not an actual path has to be specified for the Path entry. Currently .desktop files without paths (such as those from several KDE apps) explicitly passed do pass desktop-file-validate (with a warning, but not a failure). KDE can handle these just fine, but Nautilus has troubles.
The thing is that the spec is unclear about whether an unspecified path is valid.
The Desktop Entry Specification as per http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-1.1.html says the following about the value of keys which require a string:
Values of type string may contain all ASCII characters except for control characters. Unlike Values of type numeric must be a valid floating point number as recognized by the %f specifier for scanf in the C locale. which clearly states that the key value must be a valid floating point number.
String may contain ASCII chars, but may as well not do that. Numeric must include a valid floating point number, no content at all isn't meeting the requirements.
That coupled with above-mentioned desktop files passing validation makes for a very confusingly-stated standard. It also makes it hard for both sides to address the problems this ambiguous statement presents.