Stefan Sperling wrote:
> On Sun, May 10, 2009 at 09:21:41PM +0200, Frédéric Hébert wrote:
>> Back to the dev server I have made some tests, and it seems to me that
>> encoding errors are due to the presence of binary files in the dump, eg
>> files with svn:mime-type property set to application/octet-stream.
>> For example, my django project contains pure plain text in
>> 'trunk/templates' and images in 'trunk/media/images' :
>>
>> dev-server~:$ svnadmin dump -r 33
>> /var/svn/enseignements-dev.ehess.fr/ |\
>> svndumpfilter include 'trunk/templates' > \
>> /tmp/svn_enseignements_r33_nobinary.dump
>
> Do I understand correctly that you propose that Subversion
> applies the wrong mime-type settings to your text files,
> using the mime-type setting of unrelated binary files for text files?
Of course not !
That's not I wanted to say. In my dump file there are two kinds of file
content; binary file with 'application/octet-stream' mime-type and plain
text file with no svn:mime-type setted.
What I has in mind is that Subversion handles "separatly" both raw
output and encoded output in his dump file.
>
> Have you tested what happens when you set the mime-type on text files
> to 'text/plain' explicitly? It would be interesting to see if this
> fixes the problem.
>
I am sometimes (?) a kind of idiot. Of course, a dump file is himself a
binary file without encoding (a file could not contains both raw binary
and text contents). Character set is handled at import time in
Subversion internals.
I has not tested xxd on fsfs files after an import and It works. They
are utf-8.
> Stefan
Sorry about that.
Frédéric
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2176457
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-10 22:54:26 CEST