Larry Jones wrote:
=?ISO-8859-1?Q?Martin_J=F8rgensen?= writes:
First, let me get this straight: A pdf-file is binary, isn't it? ? ?
Yes.
So what I'm wondering about is that since I sometimes download files
to/from a linux system and also work on a xp system then somehow it
changed all instances of CR to CR+LF or whatever in this corrupt pdf-file?
Exactly. If the file was checked in on Windows, it may also have been
truncated (Windows interprets a ^Z in the file as end-of-file). In
general, you *must* mark binary files as binary to avoid corruption.
DAMN! I'm really fed up with tortoiseCVS now... That f***ng program is
gonna pay for that :-) Perhaps I should switch to wincvs or whatever
it's called.
Isn't there any way to tell that stupid program that *.pdf-files are
*BINARY* and not *ASCII* by default?
And now the damage is done: Anyone know how to get the file back to
normal binary again?
One pdf was taken from google. In binary format is about 399 kb. In
ascii (corrupted) format, it's 402 kb -> that's the file I can't open.
Perhaps a linux command could change the line endings back and I would
have some working pdf-files again?
Better yet: How to make tortoisecvs treat *ALL* files as binary? That
should be the best solution..... I can't believe that stupid idiotic
program thinks that *.pdf is ascii...
Best regards / Med venlig hilsen
Martin Jørgensen
--
---------------------------------------------------------------------------
Home of Martin Jørgensen - http://www.martinjoergensen.dk
_______________________________________________
info-cvs mailing list
info-cvs@nongnu.org
http://lists.nongnu.org/mailman/listinfo/info-cvs
