Re: Help with junk characters

From: Laurenz Albe <invite_at_spam.to.invalid>
Date: 04 Nov 2005 08:37:18 GMT
Message-ID: <1131093436.180313@proxy.dienste.wien.at>

News <Contact_404_at_hotmail.com> wrote:

>> - Please give an example of the junk characters.

>
> The original .dat generated with Migration toool contains for instance:
> <EOFD>Fait Mise ? jour du taux d'accident du travail appliqu? ? un
> ?tablissement<EOFD>
>
> after transferring it to unix:
> <EOFD>Fait Mise ? jour du taux d?accident du travail appliqu??
> ? un ??tablissement<EOFD>
>
> There's no problem when I put this single line into new file and I
> transfer it. The problem is when I transfer the whole .dat file.

Ah, the problem becomes much clearer.

First thing I would want you to try is to open both the .dat file that does not transfer properly and the single line file that does with the same text editor, Windows notepad for example.

Then see if the lines are really identical.

Even better would be to use a hex editor to verify that the line is the same in both files.

If you are positive that the line is the same byte sequence in both files, test the file transfer as follows:

Don't use any funky tools, use plain command line ftp:

ftp unixhost

ftp> bin
ftp> put bigfile.dat
ftp> put onelinefile
ftp> quit

Then verify that the two lines in the transferred files on the UNIX machine are the same - use 'more' or 'less' or (even better) 'od'.

Once this works, all you have to do is find out which of your Windows tools and gadgets messes up the files. Configure it appropriately or use other tools.

Yours,
Laurenz Albe Received on Fri Nov 04 2005 - 02:37:18 CST