diff options
author | Darrell Anderson <humanreadable@yahoo.com> | 2012-06-08 15:51:46 -0500 |
---|---|---|
committer | Darrell Anderson <humanreadable@yahoo.com> | 2012-06-08 15:51:46 -0500 |
commit | 6ed1ea98db6b1b369e7561efcc2c666b810e5446 (patch) | |
tree | 69da6d265387965c04a9584547ec42d4d372717d /kio/DESIGN.mimetypes | |
parent | 09d01cacf80d21ad213e6520b35e7f06e9546a83 (diff) | |
download | tdelibs-6ed1ea98db6b1b369e7561efcc2c666b810e5446.tar.gz tdelibs-6ed1ea98db6b1b369e7561efcc2c666b810e5446.zip |
Update XDG information in support of bug report 892.
Diffstat (limited to 'kio/DESIGN.mimetypes')
-rw-r--r-- | kio/DESIGN.mimetypes | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/kio/DESIGN.mimetypes b/kio/DESIGN.mimetypes index ffec64f44..7f1d81b11 100644 --- a/kio/DESIGN.mimetypes +++ b/kio/DESIGN.mimetypes @@ -1,9 +1,9 @@ TODO: servicetypes TODO: mimetypes -Service type inheritance (X-KDE-Derived) +Service type inheritance (X-TDE-Derived) ======================================== -X-KDE-Derived is for service types. ST1 derives from ST2 means ST1 is more specific than ST2. +X-TDE-Derived is for service types. ST1 derives from ST2 means ST1 is more specific than ST2. If a service implements ST1, it also implements ST2, but not the other way round. For instance, KoDocument derives from KParts/ReadWritePart, which derives from KParts/ReadOnlyPart, @@ -16,19 +16,19 @@ We need a mechanism to also say that "text/xml is a special case of text/plain", or "text/docbook is a kind of text/sgml", or "application/x-smb-workgroup is a kind of inode/directory", etc. See below. -Why mimetype "inheritance" doesn't use X-KDE-Derived +Why mimetype "inheritance" doesn't use X-TDE-Derived ==================================================== The confusing thing is that we said "a mimetype is a servicetype". But that's not exactly correct. As Waldo noted, "the ability to open a mimetype" is what's a servicetype. -So if text/xml said X-KDE-Derived=text/plain (i.e. ST1=text/xml, ST2=text/plain), +So if text/xml said X-TDE-Derived=text/plain (i.e. ST1=text/xml, ST2=text/plain), then an application opening text/xml (ST1) could also open text/plain (ST2) - which is not necessarily true. We want the other way round: to be able to open special kinds of text/plain in a plain text editor. -This is what X-KDE-IsAlso was introduced for. X-KDE-IsAlso kind of "works the other way" than X-KDE-Derived. +This is what X-TDE-IsAlso was introduced for. X-TDE-IsAlso kind of "works the other way" than X-TDE-Derived. If M1 is a special kind of M2 (mimetypes), then "the ability to open M2" derives from "the ability to open M1" -So we say in text/xml: X-KDE-IsAlso=text/plain, and applications that can open text/plain can also open text/xml. +So we say in text/xml: X-TDE-IsAlso=text/plain, and applications that can open text/plain can also open text/xml. Pattern Accuracy ====================== In some cases of inheritance several mimetypes shares the same extension (with the primary case being Ogg Multimedia files). -This has been solved sofar by matching the extension to most generic mimetype. To indicate that the mimetype can be refined further, the flag X-KDE-PatternsAccuracy can be set. The value to X-KDE-PatternsAccuracy is a number between 0-100, with 100 being the default if not set. Any values below 100 is interpreted as the possibility of further mimetype refinement. +This has been solved sofar by matching the extension to most generic mimetype. To indicate that the mimetype can be refined further, the flag X-TDE-PatternsAccuracy can be set. The value to X-TDE-PatternsAccuracy is a number between 0-100, with 100 being the default if not set. Any values below 100 is interpreted as the possibility of further mimetype refinement. |