🚀 go-pugleaf

Yes, you've hit on an interesting area.  It turns out that the really 
interesting thing is PostScript itself.  In the process of designing MIME,
we have probably had a dozen separate occasions where people have brought
up the subject of PostScript and used it as an example for why a great
deal of additional mechanism might be desired.  Trouble is, a secodn 
example is always very hard to find.  I think the bottom line is that
PostScript is a very special case.  Rather than make a really sweeping
and strange solution like multiple content-type headers, I'd prefer to
look at PostScript as PostScript, and see if it can be solved within
the existing framework, taking its idiosyncrasy into account.

The biggest problem with PS, of course, is that there are so many different
ways of using it and no real standard.  But I don't think that needs to
stop us.  Imagine, instead, that we just add a few more parameters to
the ones defined for application/postscript:

Content-type: application/postscript; subset=eps

With the addition of a parameter such as "subset" we can probably do 
everything you want -- encapsulated PS is certainly a subset, as is idraw ps.
How would you feel about just defining, registering, etc. such a 
parameter?\

By the way, I'm dragging Ned Freed into this discussion because he's
much more of a PS expert than I am.  Hope you don't mind.  -- Nathaniel