Re: Post-RFC item types

On 05/04/21 00:57,
Zachary Lee Andrews <[email protected]> put forth the proposition:
> Hello folks,
> I am wondering if all modern clients have adapted all of the item types
> supported by the UMN client and Lynx (libwww) which were not in RFC1436.
> In libwww and Lynx they're defined in HTGopher.c
> I am assuming that everybody has got the i item type supported by now (lol).
> But what about w? I think w is far better than the GET%20/ or the
> hURL hacks.
> For reference here are the item types I am referring to.
> h     HTML
> s     sound file
> w     WWW address
> :     Gopher plus image
> ;     Gopher plus movie
> <     Gopher plus sound
> P     Gopher plus PDF
> Examples of w itemtype
> :

While going through the gopher source in elinks, I found this list of
entities, although I'm not sure how well it supports the more exotic
ones, but it has options for handling custom mimetypes:

GOPHER_FILE             = '0',
GOPHER_DIRECTORY        = '1',
GOPHER_CSO              = '2',
GOPHER_ERROR            = '3',
GOPHER_MACBINHEX        = '4',
GOPHER_PCBINARY         = '5',
GOPHER_UUENCODED        = '6',
GOPHER_INDEX            = '7',
GOPHER_TELNET           = '8',
GOPHER_BINARY           = '9',
GOPHER_GIF              = 'g',
GOPHER_HTML             = 'h', /* HTML */
GOPHER_CHTML            = 'H', /* HTML */
GOPHER_MIME             = 'm',
GOPHER_SOUND            = 's',
GOPHER_WWW              = 'w', /* W3 address */
GOPHER_IMAGE            = 'I',
GOPHER_TN3270           = 'T',
GOPHER_INFO             = 'i', /* Information or separator line */
GOPHER_DUPLICATE        = '+',
GOPHER_PLUS_IMAGE       = ':', /* Addition from Gopher Plus */
GOPHER_PLUS_MOVIE       = ';',
GOPHER_PLUS_SOUND       = '<',
GOPHER_PLUS_PDF         = 'P',

http://tty1.uk/scripts/elinks/entity-types.txt

--
Dave