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

Re: problems with mimetype of and empty utf8 files in svn 1.7

From: Tomáš Bihary <bihary.t_at_st-software.com>
Date: Fri, 21 Oct 2011 13:36:53 +0200

To be honest, I expect that a C# source code will be handled as a text file.
Even if it is empty at the point of the ADD operation.

The backgound is that this happens in combination VS2008/2010 -
Resharper - VisualSVN - TortioseSVN.

If you do in Resharper the rectoring "Move the class to new file", if
first creates the empty file (just BOM).
VisualSVN reacts on it immediatelly by adding the file to svn. The new
file content is written after that.

So just common scenario for many delevopers using these tools.

But I tested it with commandline svn and there it works the same way -
empty (only with BOM) utf8 file is handled as binnary.


> What do you expect to happen?
> As to special-casing svn_io_is_binary_data() to handle 0xEFBBBF
> correctly... we could do that, I suppose.
> Tomáš Bihary wrote on Fri, Oct 21, 2011 at 11:15:19 +0200:
>> Hello,
>> after upgrading the svn 1.7 I realized an issue.
>> When I add an empty UTF-8 file, it is added with mimetype
>> application/octet-stream
>> The empty UTF8 file has 3 bytes size - there are just the 3 mark
>> bytes 0xEF 0xBB 0xBF
>> If there is an content in that file, it is handled correctly like text.
>> I've found a similar issue 2194 with UTF-16 files which status is REOPENED.
>> Regards
>> Tomas
Received on 2011-10-21 13:37:17 CEST

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.