Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!ogicse!zephyr.ens.tek.com!uw-beaver!sumax!polari!georgf
From: georgf@polari.UUCP (George Forsman)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: Decoded files are double spaced using UUDECODE?
Message-ID: <1388@polari.UUCP>
Date: 18 Mar 90 09:25:43 GMT
References: <18822.26015aaa@merrimack.edu>
Reply-To: georgf@.UUCP (George Forsman)
Organization: PolarServ, Seattle WA
Lines: 25

In article <18822.26015aaa@merrimack.edu> ain149e1@merrimack.edu writes:
>Hello out there.
>
> [discussion of how files become double-spaced after a uuencode/uudecode
>  cycle]
>
>Anyone have any thoughts?
>
>Kevin
>
>P.S. The source code is in C.  I have it if you are interested, let me know.

Since you mention the source, I assume that you are compiling it yourself,
and not using a "canned" executable.  My guess is that an fopen() is lurking
in there that opens the file in TEXT (cooked) mode, rather than BINARY (raw)
mode.  This will cause a translation of CR characters (0x0d) to a CR/LF pair
(0x0d/0x0a).  Since text files on an IBM already have a CR/LF pair, the
cooked file write will translate the CR into CR/LF, then proceed to write
the LF from the original CR/LF pair.

     -George

This is, of course, only a best guess at the problem.
----
uucp: ...uw-beaver!sumax!polari!georgf