On 2012-08-28 14:49:53 +0200, Christoph Anton Mitterer wrote: > Ian,... > > Again, AFAIU, IETF nor the RFCs do consider the MIME types as way to > determine what the sender/creator intends the recipient to do with it.
Perhaps it would be more clear like that: one may want to consider a script as a program/application that can be executed, in which case application/* should be used; but one may also want to regard it as text, in which case text/plain can be used. The IETF doesn't forbid such a choice. text/x-* could be regarded as non-standard variants of text/plain, while still providing language information. > Just look at IETF's handling of ecmascript and javascript types, where > text/* was deprecated. They are deprecated *for execution*. If the user wants to distribute the source, meant as visible as text, then text/plain and text/x-* are fine. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <http://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120828132004.gg19...@xvii.vinc17.org
