Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <20001128161318.18617.qmail@web109.yahoomail.com> Date: Tue, 28 Nov 2000 08:13:18 -0800 (PST) From: Earnie Boyd Subject: RE: To all of developers: please use .txt not .doc extension To: "'cygwin AT cygwin DOT com'" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii --- "Robinow, David" wrote: > > -----Original Message----- > > From: Christopher Faylor [mailto:cgf AT redhat DOT com] > > Sent: Monday, November 27, 2000 11:29 PM > > To: cygwin AT cygwin DOT com > > Subject: Re: To all of developers: please use .txt not .doc extension > > If the person who put the package together for cygwin is using .doc > > extensions, they should change to use .txt. > I can understand the argument against .doc, but I don't understand why > .txt is advisable. On the average naive user's machine double-clicking > on a "unix-like" file with .doc extension results in a readable file > whereas the same file renamed to a .txt extension starts Notepad which > can't properly handle the line endings. Based on David's logic, my opinion is that the Cygwin documentation should end in .doc. Word and wordpad both convert text files properly even with UNIX style line endings while the NOTEPAD product doesn't. Cheers, ===== Earnie Boyd mailto:earnie_boyd AT yahoo DOT com --- --- --- Cygwin: POSIX on Windows --- --- Minimalist GNU for Windows --- __________________________________________________ Do You Yahoo!? Yahoo! Shopping - Thousands of Stores. Millions of Products. http://shopping.yahoo.com/ -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com