headers
Wolfgang Zekoll | 11 Sep 2002 23:41
Picon

New Release of Gopher Client


Hello,

a new version of my gopher client for Linux is available, it's version
is 1.0.9c - I would call this a major step forward.  It's available on
gopher.happy-ent.de.

What's new?

   While I was thinking about making gopherc more useable I recognized that
I had forgotten something important, support for external viewers. So I
started adding extension based (not MIME based) external viewer and external
support, see "Viewer/Opener and Pager Support" in the "Client Features"
directory.

gopherc let's you now

      - define an external program to view so called binary files, e.g.
	use `antiword' to view doc files.

      - view HTML files by your favourite web browser (HTML support will
	be removed from gopherc).

Furthermore gopherc supports running in console mode and inside an X session.
While gopherc is still console based it supports a separate viewer/opener/pager
configuration for X.  That is you can browse HTML files with lynx/w3m/links
in the console and with Netsace/Opera/KDE inside X.

Version 1.0.9c is a quick release.  The next release will have the HTML support
because it's not longer needed and perhaps other things added.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Timm Murray | 15 Sep 2002 04:57
Favicon

Perl module


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Is anyone working on a Gopher client Perl module?  I've got one that is almost 
ready for testing.

- -- 
There should be an old-fasioned platform game starring Tux . . . and 
you hit the CD to toss Bill Gates into the lava and then see a little 
picture of RMS that says "Thanks for saving me Tux, but Linus Torvalds 
is in another castle!"
		--Seen on irc.openprojects.net, #debian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAj2D9ycACgkQqpueKcacfLSHagCgoDd7SJH26/YTzDNmD2Hn7m0m
cjQAn1jN+anodaftYXo0gBsWUOjxQ37h
=Dhtc
-----END PGP SIGNATURE-----
Permalink | Reply | 0 comments |
headers
Timm Murray | 15 Sep 2002 05:14
Favicon

Encouraging MIME types


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gopher+ makes it possible to use MIME types in a Gopher item.  I belive using 
MIME types in Gopher should be encouraged due to their greater flexibility.  
A single character item is actually less flexible than the DOS 3 char 
filename extension.

I'd like to see the following implemented:

1)  For backwards compatibility, servers must send the defined type associated 
with a file if it matches exactly with the type (with the exception layed out 
in [3]).  A file that would have a MIME type of text/text will still have a  
type of '0', GIF files will still have a type of 'g', etc.  Note that files 
with similar types would *not* use the standard Gopher types.  For instance, 
a text/html document would never be sent as a Gopher type of '0'.

2)  A new Gopher type, 'm', is to be implemented which tells a client to check 
the MIME type in the Gopher+ space.

3)  The 'I' type is to be either completely deprecated or used as a synonym 
for 'm'.  GIF files can still use the 'g' type, but any other images should 
be sent with the 'm' type and their proper MIME type.

4)  No new Gopher types are to be defined--MIME types are to be used as a 
complete replacement.  The only possible exception to this is for research 
purpases, but even then, MIME types are encouraged.

- --
(Continue reading)

Permalink | Reply | 7 comments |
headers
Cameron Kaiser | 15 Sep 2002 07:16

Re: Encouraging MIME types


> 2)  A new Gopher type, 'm', is to be implemented which tells a client to
> check the MIME type in the Gopher+ space.

This is a nice idea, but what should a non-Gopher+ client do with it?

--

-- 
----------------------------- personal page: http://www.armory.com/~spectre/ --
 Cameron Kaiser, Point Loma Nazarene University * ckaiser@...
-- I believe in getting into hot water; it keeps you clean. -- G.K. Chesterton
Permalink | Reply | 2 comments |
headers
Wolfgang Zekoll | 15 Sep 2002 12:19
Picon

Re: Encouraging MIME types


>2)  A new Gopher type, 'm', is to be implemented which tells a client to 
>check
>the MIME type in the Gopher+ space.

As Cameron mentioned non-gopher+ clients won't be able to detect the MIME type.
But as long as we are talking about MIME for gopher+ we could add a new 
subentry
to the +ADMIN block which tells a gopher+ client the MIME-type:

    +INFO: 0read meF0/readme.txtFgopher.serverF70
    +ADMIN:
     admin: ...
     lastmod: ...
     content-type: text/plain

MIME-types that have no direct gopher type mapping should be announced as
binary type `9' giving gopher0 clients the chance to make an arrangement
based on the extension, gopher+ clients should use the +ADMIN.content-type
mapping.

Regards

Wolfgang Zekoll
Permalink | Reply | 0 comments |
headers
Trevor | 15 Sep 2002 15:22
Picon

Re: Encouraging MIME types


a non-gopher+ client should just ignore it or identify it as an unknown type

----- Original Message -----
From: "Cameron Kaiser" <spectre@...>
To: <gopher@...>
Sent: Sunday, September 15, 2002 1:16 AM
Subject: [gopher] Re: Encouraging MIME types

>
> > 2)  A new Gopher type, 'm', is to be implemented which tells a client to
> > check the MIME type in the Gopher+ space.
>
> This is a nice idea, but what should a non-Gopher+ client do with it?
>
> --
> ----------------------------- personal page:
http://www.armory.com/~spectre/ --
>  Cameron Kaiser, Point Loma Nazarene University *
ckaiser@...
> -- I believe in getting into hot water; it keeps you clean. -- G.K.
Chesterton
>
>
Permalink | Reply | 0 comments |
headers
Timm Murray | 15 Sep 2002 20:57
Favicon

Re: Encouraging MIME types


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday 15 September 2002 00:16, Cameron Kaiser wrote:
> > 2)  A new Gopher type, 'm', is to be implemented which tells a client to
> > check the MIME type in the Gopher+ space.
>
> This is a nice idea, but what should a non-Gopher+ client do with it?

Non-Gopher+ clients are why currently defined Gopher types should still be 
used (excepting 'I').

- -- 
X windows:  Belongs to the problem set more than the solution set.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAj2E2CQACgkQqpueKcacfLTdsQCcDJR7mBqQCxHjgGMLreyqQex0
H28Ani/iBO++xc45TTvmfiUktjnsY+UP
=YR/c
-----END PGP SIGNATURE-----
Permalink | Reply | 0 comments |
headers
John Goerzen | 16 Sep 2002 04:32
Favicon

Re: Encouraging MIME types


On Sat, Sep 14, 2002 at 10:14:32PM -0500, Timm Murray wrote:

> text/text will still have a type of '0', GIF files will still have a type

I assume you mean text/plain.

> of 'g', etc.  Note that files with similar types would *not* use the
> standard Gopher types.  For instance, a text/html document would never be
> sent as a Gopher type of '0'.

text/html is type 'h' anyway.  However, type 0 is defined to include more
than you are defining it to mean.

> 2)  A new Gopher type, 'm', is to be implemented which tells a client to check 
> the MIME type in the Gopher+ space.

A Gopher+-aware client should already be doing this; there is no need to
explicitly tell it to.

> 3)  The 'I' type is to be either completely deprecated or used as a synonym 
> for 'm'.  GIF files can still use the 'g' type, but any other images should 
> be sent with the 'm' type and their proper MIME type.

This breaks backwards compatibility, I suspect.

> 4)  No new Gopher types are to be defined--MIME types are to be used as a 
> complete replacement.  The only possible exception to this is for research 
> purpases, but even then, MIME types are encouraged.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Timm Murray | 16 Sep 2002 22:14
Favicon

Re: Encouraging MIME types


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday 15 September 2002 08:31, Thomas Thurman wrote:
> On Sun, 15 Sep 2002, Trevor wrote:
> > Cameron Kaiser wrote:
> > > > 2)  A new Gopher type, 'm', is to be implemented which tells a client
> > > > to check the MIME type in the Gopher+ space.
> > >
> > > This is a nice idea, but what should a non-Gopher+ client do with it?
> >
> > a non-gopher+ client should just ignore it or identify it as an unknown
> > type
>
> Perhaps we could have another type to pass the MIME type into gopher0
> clients: say '^' could mean that the label part of the line contains the
> MIME type of the most recent line of type 'm'.
<snip>

I would assume that any clients that don't support Gopher+ now (or won't do so 
soon) aren't being updated anyway.  So it's rather silly to add anything new 
to the Gopher0 protocol.

- -- 
X windows:  The Cutting Edge of Obsolenscence.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
(Continue reading)

Permalink | Reply | 1 comment |
headers
Timm Murray | 17 Sep 2002 04:55
Favicon

Re: Encouraging MIME types


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday 15 September 2002 21:32, John Goerzen wrote:
> On Sat, Sep 14, 2002 at 10:14:32PM -0500, Timm Murray wrote:
> > text/text will still have a type of '0', GIF files will still have a type
>
> I assume you mean text/plain.

Oops, you're right.

>
> > of 'g', etc.  Note that files with similar types would *not* use the
> > standard Gopher types.  For instance, a text/html document would never be
> > sent as a Gopher type of '0'.
>
> text/html is type 'h' anyway.  However, type 0 is defined to include more
> than you are defining it to mean.

Yes.  I am intentionaly redefining the '0' type to be only text/plain 
documents.

Where was the 'h' type defined?  It wasn't in RFC 1436, and I didn't see it in 
the Gopher+ doc, either.

>
> > 2)  A new Gopher type, 'm', is to be implemented which tells a client to
> > check the MIME type in the Gopher+ space.
>
(Continue reading)

Permalink | Reply | 0 comments |

Gmane