Received: with ECARTIS (v1.0.0; list gopher); Wed, 27 Mar 2002 10:43:52 -0500 (EST) Return-Path: <jgoerzen@complete.org> Delivered-To: gopher@complete.org Received: from christoph.complete.org (unknown [168.215.193.254]) by pi.glockenspiel.complete.org (Postfix) with ESMTP id C34173B80B for <gopher@complete.org>; Wed, 27 Mar 2002 10:43:51 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by christoph.complete.org (Postfix) with ESMTP id 7065C5A483 for <gopher@complete.org>; Wed, 27 Mar 2002 10:43:50 -0500 (EST) Date: Wed, 27 Mar 2002 10:43:50 -0500 Subject: [gopher] Re: Existing \r\n Behaviour Content-type: text/plain; charset=US-ASCII Mime-Version: 1.0 (Apple Message framework v481) From: John Goerzen <jgoerzen@complete.org> To: gopher@complete.org Content-Transfer-Encoding: 8bit In-Reply-To: <3C9BFB0C.5B519894@sympatico.ca> Message-Id: <6EF3872E-4199-11D6-863F-0003930BF072@complete.org> X-Mailer: Apple Mail (2.481) X-archive-position: 536 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: jgoerzen@complete.org Precedence: bulk Reply-to: gopher@complete.org List-help: <mailto:ecartis@complete.org?Subject=help> List-unsubscribe: <mailto:gopher-request@complete.org?Subject=unsubscribe> List-software: Ecartis version 1.0.0 List-ID: Gopher <gopher.complete.org> X-List-ID: Gopher <gopher.complete.org> List-subscribe: <mailto:gopher-request@complete.org?Subject=subscribe> List-owner: <mailto:jgoerzen@complete.org> List-post: <mailto:gopher@complete.org> List-archive: <http://www.complete.org/mailinglists/archives/> X-list: gopher

On Friday, March 22, 2002, at 10:48 PM, Ralph Furmaniak wrote:

> 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

I'm a bit lost -- where exactly does this translation occur? Nothing in the RFC or Gopher+ spec seems to indicate it.

> \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).

UMN gopherd has some issues with correctly identifying file types. That's one reason I'm working on pygopherd right now. Perhaps it can one day be a drop-in replacement.

-- John