Received: with ECARTIS (v1.0.0; list gopher); Mon, 15 Apr 2002 10:34:04 -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 B71573B811 for <gopher@complete.org>; Mon, 15 Apr 2002 10:34:03 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by christoph.complete.org (Postfix) with ESMTP id F3DFE5A2D4 for <gopher@complete.org>; Mon, 15 Apr 2002 10:34:02 -0500 (EST) Date: Mon, 15 Apr 2002 10:34:02 -0500 Mime-Version: 1.0 (Apple Message framework v481) Content-type: text/plain; charset=US-ASCII Subject: [gopher] The handling of +ABSTRACT From: John Goerzen <jgoerzen@complete.org> To: gopher@complete.org Content-Transfer-Encoding: 8bit Message-Id: <36784F3C-5086-11D6-B04F-0003930BF072@complete.org> X-Mailer: Apple Mail (2.481) X-archive-position: 583 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

Hi,

Some time back, somebody in this group mentioned that he would like to see the use of +ABSTRACT increased -- possibly for future use as a right-clickable item in a filesystem browser, for instance. I think that's a great idea.

I would like to figure out what a good way to specify the +ABSTRACT attribute would be. I do not know how (or if) Ralph's gophermap files support specifying that attribute (Ralph?) UMN supports two formats:

* An Abstract= line in .Links/.names/.cap * A filename.abstract file containing the abstract.

Pygopherd will be supporting both of these in 0.9.5.

Also, I am planning to add a customizable feature whereby abstracts will be rendered as info lines following the regular menu entry for non-Gopher+ clients and similarly for HTTP clients.

I will see if an extra indicator can be presented for UMN gopher so that clients can see the availability of the abstract information. Perhaps gopherc can get a similar on-screen indicator?

-- John