Re: Fun with svn:mime-type

Greg Hudson <ghudson@MIT.EDU> writes:
> > * Is just adding the encoding to svn:mime-type the correct slution,
> > or should I use it only as a temporary hack? Should we introduce a
> > svn:encoding property instead?
>
> No idea here; maybe Greg has an opinion.

I _think_ tacking the charcoding onto svn:mime-type is the thing to
do...

Reasoning:

If we add a new property, then people will always have to ask
themselves "Do I use svn:mime-type to specify the charset encoding, if
I'm also specifying a mime type anyway, or should I *still* use the
svn:encoding property? And what would happen if I did both but they
differed?"

Conversely, if you're setting the charset encoding explicitly, it's a
no-brainer to set the mime type while you're at it. After all, if you
can't decide on a mime type, then "text/plain" is your friend :-).

In other words, since people will guess that it is *possible* to do it
on the mime-type anyway, we should just make that the official,
advertised way to do it.

-K

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 8 07:34:28 2002