Re: About the media types text/x-php and text/x-php-source
Vincent Lefevre <vincent@vinc17.net> writes:
> On 2012-08-26 19:55:49 +0200, Christoph Anton Mitterer wrote:
>> Now obviously there's a small border; I guess IETF's idea is: "Can it
>> be exectued/interpreted directly or by some interpreter? Then
>> application/*"
> Or compiled & executed, I suppose.
> But what if the intent is to display the source (with specific style),
> not to run it?
Yes, switching from text/* media types to application/* media types for
scripting languages is quite annoying for email. There are a fair number
of email clients out there that, rightly or wrongly, will not display
inline attachments of type application/*, but will do so for text/*. This
switch therefore means that attached scripts have to be saved and opened
separately rather than viewed directly inline in the mail client, which is
occasionally quite awkward. Or, alternately, one has to attach scripts as
text/plain, thus losing the language information that could otherwise be
conveyed. (There are some, although not many, mail clients that, given
proper MIME tagging of language information, will do syntax highlighting
of attached code.)
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: