True. But when you actually try to verify correctness of the import against the CVS checkout, it is kind of a dealbreaker.
Well, yes, but it also a feature which is nice to have. It's much easier for people to edit the files if they get them with their native EOL format.
Then again, we _could_ set eol-style "crlf" on all files which are obviously Windows-related. That shouldn't reduce the usability much, and would allow an automatic verification to be made, as long as you run it on UNIX.
As for other files, I'm not sure, but *any* binary file is suspect. I suggest you briefly run through the repository and look for anything binary. I only remember the graphics files as a recurring event, not quite sure if there weren't any other binary files in there which got corrupted.
As I said, I had forgotten to give a MIME database to the script. When running without a MIME database, the script relies on the -kb indicator in CVS to determine if the file is binary or not. But as you have discovered, that's not very reliable at all. When it _has_ a MIME database, it will instead treat all files as binary unless they have a text/* MIME-type.