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

Re: Classifying files as binary or text

From: Stefan Sperling <stsp_at_elego.de>
Date: Fri, 13 Nov 2009 00:34:53 +0100

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.

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=2417312
Received on 2009-11-13 00:35:16 CET

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

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