From:	jqb AT netcom DOT com (Jim Balter)
Subject:	Re: ASCII and BINARY files. Why?
29 Jan 1997 22:12:50 -0800 :
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<32F01635.55B8.cygnus.gnu-win32@netcom.com>
References:	<c=US%a=_%p=Amulet._Inc.%l=JAGUAR-970129235315Z-7391 AT jaguar DOT amulet DOT com>
Mime-Version:	1.0
X-Mailer:	Mozilla 3.01Gold (WinNT; I)
Original-To:	Fran Litterio <franl AT amulet DOT com>
Original-CC:	"'gnu-win32 AT cygnus DOT com'" <gnu-win32 AT cygnus DOT com>
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

Fran Litterio wrote:
> I just tried Notepad under NT 4.0 Workstation, and it works fine on text
> files lacking any CRs.  In fact, after editting a NL-terminated text
> file with Notepad and saving it, the file still doesn't contain CRNL
> sequences!  If I didn't know better, I'd say Microsoft has _deprectated_
> the use of CR in text-files.

Did you check the file size to be *sure* that it does not contain CR's?
On my NT 4.0 system, Notepad shows naked linefeeds as solid blocks
and does not break the line after them.

> >and the WinZip internal file viewer
> 
> Ditto.  I just tried it and it works fine with a text file lacking CRs.

Mine shows linefeeds as something like a reverse-video O.
I strongly suspect cockpit error.

> >and probably plenty of others.
> 
> I can't find any NT 4.0 app that reacts badly to a text file that's
> missing CRs.

Perhaps you should share your test file.
Or try it again with, say, \WINNT\ShellIconCache

> >The current situation is that, even fixing things like gzip,
> >the rest of the tools are useless on help files, executables,
> >databases, or any other sort of file that isn't a "text" file.
> 
> But not if gnu-win32 goes all-binary-all-the-time, correct?

Right; by "the current situation" I meant "text" mode.

> I agree that if a friend gives you a text file containing CRNL newline
> sequences, then gnu-win32 tools will preserve those ^Ms.  But that's no
> different than if you're on a UNIX workstation and someone mails you
> such a text file or it you download it via HTTP.

Exactly.  unix deals with byte streams, and there are many tools for
manipulating them, rather than having systems that think
they know what they are doing deleting every byte after a ^Z
and destroying valuable work.

> UNIX folks have been
> typing
> 
>         tr -d '\015' <dosfile >unixfile
> 
> >ever since PCs began connecting to the net.

Or putting it into a script and using it as a filter.

--
<J Q B>
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -