From owner-freebsd-doc Tue Dec 14 14:16:53 1999 Delivered-To: freebsd-doc@freebsd.org Received: from ccssu.crimea.ua (ccssu.ccssu.crimea.ua [62.244.13.130]) by hub.freebsd.org (Postfix) with ESMTP id 7CC151533D; Tue, 14 Dec 1999 14:16:40 -0800 (PST) (envelope-from phantom@scorpion.crimea.ua) Received: (from uucp@localhost) by ccssu.crimea.ua (8.9.3/8.9.0) with UUCP id AAA09958; Wed, 15 Dec 1999 00:08:14 +0200 Received: (from phantom@localhost) by scorpion.crimea.ua (8.8.8/8.8.5+ssl+keepalive) id WAA15865; Tue, 14 Dec 1999 22:57:05 +0300 (MSK) Date: Tue, 14 Dec 1999 22:57:04 +0300 From: Alexey Zelkin To: Nik Clayton Cc: doc@FreeBSD.ORG Subject: Re: TRANS: w3m instead of lynx for plain text from DocBook? Message-ID: <19991214225704.B15720@scorpion.crimea.ua> References: <19991214153042.B66677@catkin.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i In-Reply-To: <19991214153042.B66677@catkin.nothing-going-on.org> X-Operating-System: FreeBSD 2.2.7-RELEASE i386 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hi, On Tue, Dec 14, 1999 at 03:30:42PM +0000, Nik Clayton wrote: > I've been playing with w3m (ports/www/w3m), which is a lynx replacement. > Apart from being somewhat nicer to use than lynx, and a quarter of the > size (231,244 bytes, versus 862,648 bytes), w3m also handles tables (and > even frames, which we don't use). Good points, but what about multiple encodings support ? I think it's big point for non-english users/developers (at least for me) > [...] > ${DOC}.txt: ${DOC}.html > - lynx -nolist -dump ${.ALLSRC} > ${.TARGET} > + w3m -S -dump ${.ALLSRC} > ${.TARGET} > [...] BROWSER=w3m BROWSEROPTS=-S -dump ${DOC}.txt: ${DOC}.html ${BROWSER} ${BROWSEROPTS} ${.ALLSRC} > ${.TARGET} Comments ? -- /* Alexey Zelkin && phantom@cris.net */ /* Tavric National University && phantom@crimea.edu */ /* http://www.ccssu.crimea.ua/~phantom && phantom@FreeBSD.org */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message