From: Cameron Kaiser <spectre@floodgap.com>
Message-Id: <200711120344.lAC3iR74004902@floodgap.com>
Subject: [gopher] Re: GOPHER file format.
In-Reply-To: <Pine.NEB.4.64.0711120332430.8287@otaku.freeshell.org> from Pawel
 at "Nov 12, 7 03:39:41 am"
To: gopher@complete.org
Date: Sun, 11 Nov 2007 19:44:27 -0800 (PST)
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org

> It is anything like universal gopher file format ?
> In the HTTP world i can use the *same* html document on any HTTP
> server without problem. And what abbout GOPHER ?
> 
> It is any universal form or its always depend on gopher sever ?
> In exampe on SDF's gopherd when i wish to create link to files, I 
> must(?) use .links files with contents like:
> 
> Name=BIO
> Type=0
> Path=./bio.txt
> Numb=1
> 
> It is a standard and universal way ?

This is the UMN links style, which is the most common format, and is supported
in pygopherd as well.

Bucktooth does not support it, and some other newer servers might not. The
reason Bucktooth doesn't is simply because I think the format sucked, but I
do freely admit this wasn't nice for compatibility.

-- 
------------------------------------ personal: http://www.cameronkaiser.com/ --
  Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckaiser@floodgap.com
-- It is one thing to praise discipline, and another to submit to it.-Cervantes