Received: with ECARTIS (v1.0.0; list gopher); Fri, 22 Mar 2002 22:50:02 -0500 (EST) Return-Path: Delivered-To: gopher@complete.org Received: from tomts21-srv.bellnexxia.net (tomts21.bellnexxia.net [209.226.175.183]) by pi.glockenspiel.complete.org (Postfix) with ESMTP id 187E83B80D for ; Fri, 22 Mar 2002 22:50:01 -0500 (EST) Received: from sympatico.ca ([64.228.194.67]) by tomts21-srv.bellnexxia.net (InterMail vM.4.01.03.23 201-229-121-123-20010418) with ESMTP id <20020323034959.EDVV27110.tomts21-srv.bellnexxia.net@sympatico.ca> for ; Fri, 22 Mar 2002 22:49:59 -0500 Message-ID: <3C9BFB0C.5B519894@sympatico.ca> Date: Fri, 22 Mar 2002 22:48:28 -0500 From: Ralph Furmaniak X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Gopher-L Subject: [gopher] Existing \r\n Behaviour Content-type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-archive-position: 532 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: sugaku@sympatico.ca Precedence: bulk Reply-to: gopher@complete.org List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-ID: Gopher X-List-ID: Gopher List-subscribe: List-owner: List-post: List-archive: X-list: gopher While we're looking for things to ammend, how about the translation \n -> \r\n in files. Nowadays, there is no problem if the files just have \n (unless you are using notepad, but who is?). But the problem is that if you do this to a unix script file (shell, perl, etc) it will no longer work, because of the \r at the end of the first line (ie, it would try to execute /usr/bin/perl\r). It also breaks other things such as pdf files (which are a mix of text and binary, and are reported to be text files).