Projects/Oxygen/namingSpec/mimetypes: Difference between revisions
Line 60: | Line 60: | ||
===Other MIME types needed for KDE=== | ===Other MIME types needed for KDE=== | ||
<pre> | <pre> | ||
application-x-bittorrent | application-x-bittorrent OK | ||
x-office-wordprocessing | x-office-wordprocessing | ||
</pre> | </pre> |
Revision as of 20:44, 25 July 2007
Specification compliance of icon names
With MIME types, there is no complete list of icon names in the spec. Therefore, they are divided in categories:
Standard FD.o MIME Types
This is the complete list in the FD.o spec:
application-x-executable <- actions/exec audio-x-generic <- sound font-x-generic image-x-generic package-x-generic text-html <- html text-x-generic <- txt text-x-generic-template text-x-script video-x-generic <- video x-office-address-book x-office-calendar x-office-document <- document x-office-presentation x-office-spreadsheet <- spreadsheet
These are included in Tango:
application-certificate text-x-preview x-office-document-template x-office-drawing x-office-drawing-template x-office-presentation-template x-office-spreadsheet-template
It has not yet been determined which Tango icons we will need to use.
Icons for Standard MIME Types
This is the complete list in the FD.o spec Non-regular files:
inode-blockdevice inode-chardevice inode-directory <- places/folder inode-fifo inode-mount-point inode-socket inode-symlink Can we use an emblem for this?
Other Non-regular MIME types needed for KDE:
inode-directory-home <- places/user-home
Other MIME types conforming to IANA
text-plain <- ascii
Note for IANA conformity, see: [1]
Other MIME types needed for KDE
application-x-bittorrent OK x-office-wordprocessing