[gopher] Re: Existing \r\n Behaviour
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
Reply to: