subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bob Archer <Bob.Arc...@amsi.com>
Subject RE: Adding Unicode files erroneously applies application/octet mime type
Date Mon, 09 May 2011 21:00:15 GMT
> 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


Mime
View raw message