Received: with ECARTIS (v1.0.0; list gopher); Sat, 30 Jun 2007 09:46:17 -0500 (CDT) Received: from static-71-170-11-156.dllstx.dsl-w.verizon.net ([71.170.11.156] helo=turquoise.pongonova.net) by glockenspiel.complete.org with esmtp (Exim 4.63) id 1I4eDI-0000aP-7c for gopher@complete.org; Sat, 30 Jun 2007 09:46:17 -0500 Received: by turquoise.pongonova.net (Postfix, from userid 1000) id 877B6674; Sat, 30 Jun 2007 08:48:36 -0500 (CDT) Date: Sat, 30 Jun 2007 08:48:36 -0500 From: brian@pongonova.net To: gopher@complete.org Subject: [gopher] Re: Bucktooth questions Message-ID: <20070630134836.GB6348@pongonova.net> References: <20070630062739.GB5388@pongonova.net> <200706301409.l5UE9ZBY015354@floodgap.com> Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200706301409.l5UE9ZBY015354@floodgap.com> User-Agent: Mutt/1.5.5.1i X-Spam-Status: No (score 0.6): AWL=0.000, NO_REAL_NAME=0.55 X-Virus-Scanned: by Exiscan on glockenspiel.complete.org at Sat, 30 Jun 2007 09:46:17 -0500 Content-Transfer-Encoding: 8bit X-archive-position: 1635 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: brian@pongonova.net 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

While we're on the topic: Does anyone know of a html->gopher converter? Something that basically converts HTML tags that can be converted to RFC 1436-compliant syntax (i.e., prepending the correct itemtype for links, files, images, etc.), and strips out the rest.

I'm setting up a gopher proxy of sorts for WikkaWiki, and want to be able to serve up either RFC 1436-compliant pages or wiki pages. The assumption here is that Wikka is already set up and running as an HTTP service; I'm writing a proxy that would intercept a gopher request, retrieve the wiki page via HTTP, pass it on if it's RFC 1436-compliant, or convert/strip out html as appropriate. I just don't like to reinvent the wheel when I can avoid it.

All of this would probably work better with a flat-file-based wiki like PmWiki (I'd be able to access pages directly), but I'm partial to Wikka for a number of reasons...

--Brian