I had this problem also.  I was converting CVSNT to SVN.  My
Word doc 
had Unicode file format (-kv in CVSNT) which is not
supported by CVS.  
This caused conversion to garble it.  I had other Word docs
which were 
binary files and the conversion was fine.  I think you can
change the 
file type to binary in CVS, then conversion will work fine. 
I did not 
try it.  I ended up deleting the file and re-adding it in
SVN.

Best regards,
Tony



jmedalenmicron.com wrote:
> Our platform is XP.
>
> Case sensitivity doesn't seem to be an issue; the name
in the repo
> matches the name of the file.
>
> Something interesting about properties:
> We're only having trouble (so far) with .doc and .pdf
files.
> Doing a repo/show properties on those files shows:
>    Svn:mime-type  application/msword
>    Svn:eol-style
>
> Should "svn:eol-style" be blank?
> A .sys file doesn't have the eol-style listed at all.
>
> I then did a properties on a newly added .doc file (one
there aren't
> these issues on).
> It's properties are:
>    svn:mime-type  application/octet-stream
>
> I changed the property of one of the converted files -
and now a
> modification works as expected!
> Note:  the empty "svn:eol-style" is now gone
as well.
>
> Does this make sense?
>
> Thanks,
>
> John
>
> -----Original Message-----
> From: Michael Haggerty [mailto:mhaggeralum.mit.edu] 
> Sent: Tuesday, November 06, 2007 12:53 PM
> To: jmedalen
> Cc: userscvs2svn.tigris.org
> Subject: Re: Cvs2svn conversion = word documents
unrecognized after
> modification
>
> jmedalenmicron.com wrote:
>   
>> We recently converted our CVS repository to SVN.
>> The conversion itself went fine, but we found out
that if we modify a 
>> converted word document, SVN no longer recognizes
it as an SVN file.
>>
>> This also happens if you simply resave the file
without changes.
>>
>> If you try to re-add the file, SVN complains that a
file of that name 
>> already exists.
>>
>> A newly added word file does not have this problem;
it behaves
>>     
> normally.
>   
>> Any ideas of how to correct this?
>>     
>
> This is probably more of an SVN issue than a cvs2svn
issue.
>
> What platform are you using?
>
> Could it be a case sensitivity problem?  Maybe the file
exists in the
> repository with one choice of upper/lowercase, and the
file on disk has
> another one, and that is confusing Subversion?
>
> Does the directory containing the file have a
svn:ignore property set?
> (Type "svn proplist -v directory_name".)
>
> Michael
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: users-unsubscribecvs2svn.tigris.org
> For additional commands, e-mail: users-helpcvs2svn.tigris.org
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: users-unsubscribecvs2svn.tigris.org
> For additional commands, e-mail: users-helpcvs2svn.tigris.org
>
>
>
>   

------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribecvs2svn.tigris.org
For additional commands, e-mail: users-helpcvs2svn.tigris.org