From: john_r_velman AT mail DOT hac DOT com Subject: CRLF again, was: Re[2]: smtp mail failed 16 Oct 1998 13:48:20 -0700 Message-ID: <0F0W0060R6XJ33.cygnus.gnu-win32@mail.hac.com> Mime-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="Boundary_(ID_mAziLaLqkN+h2nP37to6WQ)" To: gnu-win32 AT cygnus DOT com, marcus AT bighorn DOT dr DOT lucent DOT com --Boundary_(ID_mAziLaLqkN+h2nP37to6WQ) Content-type: TEXT/PLAIN; CHARSET=ISO-8859-1 Content-transfer-encoding: 7BIT In my opinion, all archiving and zipping programs (tar, zip, unzip, etc) should *never* add CRs where they don't exist in the source file. Likewise, *all* filters (tr, cat, pipes...) should *only* add CRs if instructed to do so on the options line. Then if someone want's to use a text file from a non windows source in a windows program that needs the CRLF combination (like this ccmail) they can run the file through a Unix to Dos filter. This CRLF business has been the most difficult thing about using the cyg-win gnu-win tools. The NT emacs I'm using seems to have some algorithm in it that decides what to do. It doesn't always do the right thing. The Vim I have is honest about it. Unless you tell it specifically something like :se ff=dos, it just seems to keep things like they were. Well, cyg-win32, gnu-win32 is still a great suite of software, but with a few growing pains. Best to all, John Velman jrvelman AT mail DOT hac DOT com ______________________________ Reply Separator _________________________________ Subject: Re: smtp mail failed Author: marcus AT bighorn DOT dr DOT lucent DOT com at mime Date: 10/14/98 9:17 AM > As I've stated on my web pages under my Personal Reflections on this > subject, IF YOU DEPEND ON THE BINARY MODE MOUNT SETTING THEN YOU ARE > MASKING A PROBLEM WHICH WILL EVENTUALLY BYTE YOU SOMEWHERE ELSE. > Consider yourself bytten. > > I suggest that you get the source code and find all of the open/fopen > statements and properly add the necessary file mode processing > switches. The only truly way to get rid of this for good is to > properly port the code and be specific about what mode your file > should be processing in. > > PORTERS OF SOFTWARE, please, don't depend on the binary mode mount > setting!! Make the appropriate changes to the open/fopen statements. While I agree 100% with this view, there are some difficulties that are particularly apparent with archive software. If tar is unpacking a file, (or packing it, for that matter) is it a binary file or a text file? Somehow, tar/zip/whatever must find out whether to open the file in text or binary mode, yet there seems to be no definitive way to tell which. Do you try to see if the file has all characters < 0x100 and line breaks every so often to call it a text file? What about various meta-character escapes (for extended character sets, bold/italic/underline, etc.). What if an executable file actually does contain '\n' every so often. These heuristics are bound to make mistakes, but what better way is there to tell? marcus hall - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help". --Boundary_(ID_mAziLaLqkN+h2nP37to6WQ) Content-type: TEXT/PLAIN; CHARSET=ISO-8859-1 Content-transfer-encoding: 7BIT RFC-822-headers: Received: from CONVERSION-DAEMON by mail.hac.com (PMDF V5.1-12 #D3246) id <0F0W009013W942 AT mail DOT hac DOT com> for "john r velman"@mime.mail.hac.com; Thu, 15 Oct 1998 15:31:22 -0700 (PDT) Received: from PROCESS-DAEMON by mail.hac.com (PMDF V5.1-12 #D3246) id <0F0W009013W941 AT mail DOT hac DOT com> for "john r velman"@mime.mail.hac.com; Thu, 15 Oct 1998 15:31:21 -0700 (PDT) Received: from fw-es05.hac.com by mail.hac.com (PMDF V5.1-12 #D3246) with ESMTP id <0F0W00MEO3W8NI AT mail DOT hac DOT com> for "john r velman"@mime.mail.hac.com; Thu, 15 Oct 1998 15:31:20 -0700 (PDT) Received: from cygnus.com ([205.180.230.5]) by fw-es05.hac.com (8.9.0/8.9.0) with ESMTP id PAA11307 for ; Thu, 15 Oct 1998 15:30:52 -0700 (PDT) Received: (from majordom AT localhost) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) id JAA20107; Wed, 14 Oct 1998 09:17:50 -0700 (PDT) Received: from algw2.lucent.com (algw2.lucent.com [205.147.213.2]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with SMTP id JAA20101 for ; Wed, 14 Oct 1998 09:17:47 -0700 (PDT) Received: from bighorn.dr.lucent.com by alig2.firewall.lucent.com (SMI-8.6/EMS-L sol2) id MAA00228; Wed, 14 Oct 1998 12:29:09 -0400 Received: by bighorn.dr.lucent.com (SMI-8.6/EMS-1.4.1 sol2) id KAA15736; Wed, 14 Oct 1998 10:17:55 -0600 Received: from chorus.dr.lucent.com by bighorn.dr.lucent.com (SMI-8.6/EMS-1.4.1 sol2) id KAA15728; Wed, 14 Oct 1998 10:17:54 -0600 Received: from chorus by chorus.dr.lucent.com (SMI-8.6/EMS-L sol2) id KAA04778; Wed, 14 Oct 1998 10:17:26 -0600 Date: Wed, 14 Oct 1998 10:17:26 -0600 (MDT) From: "139a80000-HallM(DR3132)37x10" Subject: Re: smtp mail failed Sender: owner-gnu-win32 AT cygnus DOT com Reply-to: "139a80000-HallM(DR3132)37x10" Message-id: <199810141617 DOT KAA04778 AT chorus DOT dr DOT lucent DOT com> MIME-version: 1.0 X-Mailer: dtmail 1.2.1 CDE Version 1.2.1 SunOS 5.6 sun4m sparc Content-transfer-encoding: 7BIT Precedence: bulk X-Sun-Text-type: ascii --Boundary_(ID_mAziLaLqkN+h2nP37to6WQ)-- - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".