[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Towards standardising mime-type support

From: Branko ─îibej <brane_at_xbc.nu>
Date: 2005-04-01 18:12:23 CEST

Dale Worley wrote:

>>From: Branko Cibej [mailto:brane@xbc.nu]
>>>text/x-c; charset=us-ascii
>>Well, this is clearly wrong, there's no such thing as a
>>"text/x-c" mime type.
>It seems to me that that is an overly strict interpretation. The MIME standard intends that one may use "private definition" subtypes starting with "x-" (RFC 1341, section 4, near the top of page 7). (And that is in harmony with many other places where one may use a token starting with "x-" in place of a standardized token.) For a source control system, I can see the advantage of being able to specify each programming language as a different subtype of text/*.
Certainly, if Subversion were a source control system, but not in
svn:mime-type. MIME was simply not designed for this purpose. I know
it's been abused for such things, but that doesn't mean we have to
continue this practice. Encoding the eimplementation language in the
MIME type would be wrong, just as encoding the language used in a
document would be wrong.

And there's no need for such overloading; after all, you can set
arbitrary properties in Subversion, and one of them might well be the
programming language used in the file.

But since Subversion is a version control system, not a source control
system, this kind of property doesn't really belong in the core feature set.

-- Brane

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 1 18:15:01 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.