MIME changes

[Stephan Kulow]

On Monday 12 May 2003 23:54, Andras Mantia wrote:
>  The  X-KDE-Text property was introduced because there was no reliable way to
> find out if a file is text or binary. Some applications needs to know it, as
> it doesn't make sense to open a binary file inside a text editor (or inside
> KMail and view as text). Furthermore it can even be dangerous, and you may
> not even call it a bug when the application designed to work with text files
> fails when a binary files is opened as text. Of course, it can be discussed
> what is marked as text, but script files, plain text and such surely belongs
> there. Even postscript is text, but of course not so easy to understand. ;-)
> BTW, looking if the files belongs to text/* is not enough as many (mainly for
> script files) mimetypes are under application/ . I cannot count how many
> mail/bugreports I've got from users when Quanta relied only on the mimetype
> check (for text/*) to find out if a file is text (and therefor editable) or
> not.
> 

David, can't this be implemented using the X-KDE-IsAlso=text/plain feature
we want anyway? :)

I think, definining an "inheritance" between mimetypes makes sense for more
than text files.

Greetings, Stephan