Hello,
Is it possible to improve this? Like doing the conversion before the
checking?
SVNKit 1.3.x uses a base version of a file to detect its MIME type. The
base version is always ASCII-encoded when charset conversion's on.
Since version 1.7.0 it seems to use a working version of a file. That's
not trivial to fix. Please follow this issue to get updates on it:
http://issues.tmatesoft.com/issue/SVNKIT-302
Meanwhile you may specify a proper svn:mime-type property for text
files, e.g. text/plain; you can also add an auto-property for files with
certain text extensions.
Semen Vadishev,
TMate Software,
http://subgit.com/ - git+svn on the server side!
On 8/9/12 20:27, m6m6 wrote:
Testing the details..
When I add a new member on USS it seems there is a binary check before
conversion from IBM-1047 and binary mime-type is set as svn property:
jsvn add MIDI2
A (bin) MIDI2
jsvn pl -v MIDI2
Properties on 'MIDI2':
svn:mime-type
application/octet-stream
The file looks perfectly EBCDIC:
cat MIDI2
midi member newly created
dump MIDI2
0000 94898489 40948594 82859940 9585A693 midi member newl
0010 A8408399 8581A385 840D15 y created..
Is it possible to improve this? Like doing the conversion before the
checking?
Cheers, m6m6
