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

RE: Adding Unicode files erroneously applies application/octet mime type

From: Bob Archer <Bob.Archer_at_amsi.com>
Date: Mon, 9 May 2011 17:00:15 -0400

> On May 9, 2011, at 13:49, Bob Archer wrote:
>
> > It seems when I "svn add" unicode (UCS-2 Little Endian, I think
> it is) files svn applies the svn:mime-type of application/octet to
> the files.
>
> Correct.
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=2194
>
>
> > My question is, if I remove the property and just commit the
> file... are diff and merge operations going to work fine?
>
> I highly doubt it.
>
> > Or, should I switch to plain ascii encoding?
>
> If your files can be represented in ASCII, by all means do that. If
> you need non-ASCII characters, consider using UTF-8 instead of UTF-
> 16.
>

Ok, I will just stick with ASCII for now. I don't think we need non-ascii characters for our SQL scripts at this point. It is just that our SQL scripting tool defaults to Unicode. We have just been removing the mime-type, but I will tell them to switch to outputting ASCII. Also, I'm not sure what SQL Management Studio's default is. I see a way to specify on saving a script but not on scripting to file.

thanks,
BOb
Received on 2011-05-09 23:00:45 CEST

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

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