Re: svn:charset

Sorry about the late reply - I'm used to being Cc:ed on replies to
mailing list threads in which I participate, so I didn't notice your
followup right away.

Alan Barrett <apb_at_cequrux.com> writes:
> I really don't like the idea of having two conflicting ways of
> specifying the same information. One way (in svn:mine-type) should be
> enough.

well,

 - svn:charset is easier to handle for applications that need just the
   charset, not the media type (incorrectly referred to as mime type)

 - The charset is strictly speaking not part of the MIME media type, it
   is an optional parameter for the Content-Type header used in both
   MIME and HTTP. The media type is the first (unnamed) field, and the
   only non-optional one.

 - The full MIME Content-Type parameter syntax is unwieldy. It allows a
   variety of quoting and comment styles. For instance, these two:

     Content-type: text/plain; charset=us-ascii (Plain text)
     Content-type: text/plain; charset="us-ascii"

   are equivalent, and there can be additional semicolon-separated
   parameters, such as the MIME version or anything else you feel like
   adding (as long as it starts with "x-"), which are of no use to
   Subversion. How far do you want to go to support the complete
   syntax?

 - Like it or not, svn:charset is already in use; formalizing it is the
   path of least resistance (though I understand your annoyance at the
   encroachment on what I understand is a reserved namespace)

 - My patch does not change existing behaviour for people who don't use
   svn:charset, but it improves functionality for those who do (since
   mod_dav_svn now knows about it and uses it)

DES

-- 
Dag-Erling Smørgrav - des_at_des.no
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org