From: shankar AT chromatic DOT com (Shankar Unni) Subject: Re: ASCII and BINARY files. Why? 30 Jan 1997 11:36:11 -0800 Approved: cygnus DOT gnu-win32 AT cygnus DOT com Distribution: cygnus Message-ID: <32F0E84D.6845.cygnus.gnu-win32@chromatic.com> References: <199701291949 DOT NAA04239 AT utig DOT ig DOT utexas DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.0Gold (X11; I; SunOS 5.5.1 sun4u) Original-To: Scott Kempf Original-CC: gnu-win32 AT cygnus DOT com Original-Sender: owner-gnu-win32 AT cygnus DOT com Scott Kempf wrote: > Korn's paper on UWIN says that he found that "many programs that run > on Windows NT do not require the in front of each in order > to work. This difference turned out to be less of a problem that (sic) > we had originally expected." I don't have enough experience to > evaluate this claim. It all depends on what tools you're using. Heavyweight tools like Visual C++ and the Office suite don't seem to care (e.g. if you import a text file with Unix-lile newlines into Microsoft Word, it's perfectly happy and does the right thing). It's only the dumb old Windows tools like Notepad, and the DOS MORE.COM, which don't know how to handle Unix text files. Even Wordpad does the right thing. Of course, they all *export* text files using the convention, but that's expected. -- Shankar Unni shankar AT chromatic DOT com Chromatic Research (408) 752-9488 - For help on using this list, send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".