2009/11/12 Stefan Sperling <stsp_at_elego.de>:
> On Thu, Nov 12, 2009 at 03:20:00PM -0800, Mike Samuel wrote:
>> Much of the early debate deals with svn:charset being non-standard and
>> non-approved. I tend to agree with Stefan, that this proposal
>> shouldn't gate on svn:charset being approved so I suggest tabling
>> variant 1.
>
> Yes.
>
>> http://svn.haxx.se/dev/archive-2008-06/0948.shtml
>> One argument in favor of svn:charset, independently of the above, is
>> that unlike the current trick of appending "; charset=%s" to the MIME
>> type, it works with auto-props.
>
> I guess when Dag-Erling wrote this (I took the liberty to put him in Cc
> for this post, please drop him again when following up), he didn't realise
> that you can simply escape the semicolon used to separate multiple
> properties in an autoprops specification with another semicolon.
Great. In that case, I think the only open issues are variants 2 and
3 which I'm inclined to drop because of the platform-sensitivity
issues you raised.
If no-one responds within 24 hours or so arguing for those, I'll start
implementing it without any variants.
> For example:
> ~/.subversion/config:
> enable-auto-props = yes
> [auto-props]
> *.svg = svn:mime-type=image/svg+xml;; charset=UTF-8;svn:needs-lock
>
> $ touch foo.svg
> $ svn add foo.svg
> A (bin) foo.svg
> $ svn pl foo.svg
> Properties on 'foo.svg':
> svn:needs-lock
> svn:mime-type
> $ svn pg svn:mime-type foo.svg
> image/svg+xml; charset=UTF-8
>
> Stefan
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2417316
Received on 2009-11-13 00:45:17 CET