Date: Sun, 31 Aug 2003 11:55:29 +0100
From: Luis Oliveira <luismbo@netcabo.pt>
To: gopher@complete.org
Subject: [gopher] Re: PyGopherd 2.0 released; Gopher and WAP
Message-ID: <20030831105529.GB876@nhop>
Mail-Followup-To: Luis Oliveira <luismbo@netcabo.pt>,
	gopher@complete.org
References: <20030823201547.GA5036@complete.org>
Mime-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-Disposition: inline
In-Reply-To: <20030823201547.GA5036@complete.org>
Organization: pouca, muito pouca
User-Agent: Mutt/1.5.4i
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org

On Sat, Aug 23, 2003 at 03:15:47PM -0500, John Goerzen wrote:
> To that end, PyGopherd now has built-in WAP support.  If you enable the=
 WAP
> protocol in your config file, you get WAP support for free, *including
> forms*.  As an example, you can point your WAP-enabled phone to:
>=20
> http://quux.org:70/wap

For some reason I couldn't get my phone to see that site but I'll try
again latter.

Anyway, I wonder how the gopher text entries (excuse my gopher illiteracy=
)
will look like in such a little width display. Shouldn't gopher have
better means of describing listings / single items?

Just a suggestion,

--=20
Lu=EDs Oliveira                                        Lisp is the red pi=
ll.
http://student.dei.uc.pt/~lmoliv/           -- John Fraser, comp.lang.lis=
p=20
Equipa Portuguesa do Translation Project
http://www2.iro.umontreal.ca/~pinard/po/registry.cgi?team=3Dpt