Daniel Shahaf wrote on Tue, Jun 21, 2011 at 21:54:35 +0300: > Dennis E. Hamilton wrote on Mon, Jun 20, 2011 at 20:40:58 -0700: > > No joy. > > > > Nothing I do prevents the SVN server from coughing up text files as Western > > Europe (ISO) encoding. > > > > I wonder if it was simply a coincidence that it appeared to work on the OIC > > SVN. > > > > - Dennis > > > > -----Original Message----- > > From: Dennis E. Hamilton [mailto:[email protected]] > > Sent: Monday, June 20, 2011 19:27 > > To: '[email protected]' > > Cc: '[email protected]' > > Subject: RE: svn commit: r1137103 - in /incubator/ooo/site: ./ trunk/ > > trunk/cgi-bin/ trunk/content/ trunk/content/openofficeorg/ > > trunk/content/openofficeorg/css/ trunk/content/openofficeorg/docs/ > > trunk/content/openofficeorg/docs/governance/ trunk/content/open > > > > I looked at the properties on folders in my working copies and I have no > > issue tracker integration. The TortoiseSVN settings on my computer have no > > Issue Tracker Hooks and there are no SVN properties being asserted > > automatically on folders. > > > > So I think I'm in the clear. I'm always running the latest TortoiseSVN > > (64-bit if that matters). > > > > - Dennis > > > > I was still bummed that I can't set > > > > *.txt=svn:mime-type=text/plain;charset=UTF-8 > > > > Need to escape the semicolon here. I /think/ that we recently patched > some escaping syntax, but I can't find it right now... > > /me looks at Greg >
It seems that double semicolon is the escape syntax, ie *.txt = svn:mime-type=text/plain;; charset=UTF-8 see split_props() in https://svn.apache.org/repos/asf/subversion/trunk/subversion/libsvn_client/add.c > > I was certain I'd figured out how to do it for the OIC SVN, but those > > TortoiseSVN and SVN clients were on a machine I don't have any more (sigh). > > > > I FOUND IT IN MY OIC SVN WORKING FOLDER on my home server. SVN appears to > > recognizes a mime.types file in a repository folder, and autoprops are > > additive to that. (Or the web server is doing it. I don't care.) > > > > I switched to doing all MIME types in the file and using autoprops in the > > client only for other things. Hmm. I do love that I narrate my repos: > > <http://tools.oasis-open.org/version-control/svn/oic/SpecAnalysis/mime.types> > > (and that applies to .types too, if you check your browser encoding > > selection for viewing that page). > > > > I must experiment with this. I know a good place. > > > > > > -----Original Message----- > > From: Rob Weir [mailto:[email protected]] > > Sent: Saturday, June 18, 2011 05:29 > > To: [email protected] > > Subject: Re: svn commit: r1137103 - in /incubator/ooo/site: ./ trunk/ > > trunk/cgi-bin/ trunk/content/ trunk/content/openofficeorg/ > > trunk/content/openofficeorg/css/ trunk/content/openofficeorg/docs/ > > trunk/content/openofficeorg/docs/governance/ trunk/content/open > > > > On Fri, Jun 17, 2011 at 11:55 PM, Greg Stein <[email protected]> wrote: > > > > [ ... ] > > > > Propchange: incubator/ooo/site/trunk/content/openofficeorg/ > > > > > > > ------------------------------------------------------------------------------ > > > > bugtraq:number = true > > > > > > > > Propchange: incubator/ooo/site/trunk/content/openofficeorg/css/ > > > > > > > ------------------------------------------------------------------------------ > > > > bugtraq:number = true > > > > > > Hunh? What is this? > > > > > > Is there a particular reason for this, or can we nuke the property? > > > > > > I imagine we probably need to apply svn:eol-style to many of the files, > > > too. > > > > > > Cheers, > > > -g > > > > > > > TortoiseSVN is adding them by default. We don't need them. I'll disable. > > Dennis should watch out as well, since he is using Tortoise too. > > > > -Rob > >
