X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f996b,fdff6929bbc2b6a1
X-Google-Attributes: gidf996b,public
X-Google-Thread: fbb9d,fdff6929bbc2b6a1
X-Google-Attributes: gidfbb9d,public
X-Google-ArrivalTime: 1995-01-12 04:27:30 PST
Path: 
 nntp.gmd.de!dearn!blekul11!idefix.CS.kuleuven.ac.be!ub4b!EU.net!Germany.EU.net!
 howland.reston.ans.net!news.sprintlink.net!sashimi.wwa.com!not-for-mail
From: brett@prospero.dev.cdx.mot.com (Brett Miller)
Newsgroups: alt.ascii-art,rec.arts.ascii
Subject: Talk: Uploading and Trailing M's
Date: 11 Jan 1995 18:03:10 -0600
Organization: Motorola Information Systems Group, Mansfield, MA
Lines: 26
Sender: boba@gagme.wwa.com
Approved: boba@wwa.com
Message-ID: <3f1rju$7g9@gagme.wwa.com>
References: <9501101909.aa24584@sfa.sfa.ope.ed.gov> <3f01ta$im4@gagme.wwa.com>
NNTP-Posting-Host: gagme.wwa.com
Xref: nntp.gmd.de alt.ascii-art:18888 rec.arts.ascii:3552


In article <3f01ta$im4@gagme.wwa.com>,
Daniel Au <dcau@casbah.acns.nwu.edu> wrote:
>
>Does anyone else have problems with such as the one below...I assume that the
>person uploaded a file and got all the trailing M's, which I know occurs with
>any text file because it happens to me too.
>
>Is there any way to remove the trailing ^M's instead of doing it by hand,
>which is what I'm doing now?  Sometimes, if the file is long, it can be
>_tremendously_ frustrating.  Any help would be appreciated.
>

Daniel,

I think that this is caused by a DOS<->UNIX translation.  If you do your
file transfers as text instead of binary you shouldn't have the problem.
If you have files that already contain the ^M's try using the unix2dos
or dos2unix commands to remove them.  I don't remember which you'll want
to use in this particular case.

Hope this is right and helps,
-Brett