From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: terminal escapes in Info files? Date: 29 Oct 2003 20:47:46 +0100 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <200310280126.h9S1Q9N16202@f7.net> <20031028105102.GA7330@dirtyweb.penguinpowered.com> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1067458764 1735 80.91.224.253 (29 Oct 2003 20:19:24 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 29 Oct 2003 20:19:24 +0000 (UTC) Cc: eliz@elta.co.il, emacs-devel@gnu.org, Stefan Monnier , dirt@gtk.org, karl@freefriends.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Wed Oct 29 21:19:20 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1AEwmm-0001Xd-00 for ; Wed, 29 Oct 2003 21:19:20 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1AEwmm-0003re-00 for ; Wed, 29 Oct 2003 21:19:20 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AEwlx-0002zl-FO for emacs-devel@quimby.gnus.org; Wed, 29 Oct 2003 15:18:29 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1AEwJk-0005nJ-5H for emacs-devel@gnu.org; Wed, 29 Oct 2003 14:49:20 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1AEwJ8-0005Xu-2x for emacs-devel@gnu.org; Wed, 29 Oct 2003 14:49:13 -0500 Original-Received: from [217.80.160.85] (helo=localhost.localdomain) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.24) id 1AEwIV-0005CS-Sr; Wed, 29 Oct 2003 14:48:04 -0500 Original-Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.12.8/8.12.8) with ESMTP id h9TJlsl5010810 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 29 Oct 2003 20:47:55 +0100 Original-Received: (from dak@localhost) by localhost.localdomain (8.12.8/8.12.8/Submit) id h9TJllE6010806; Wed, 29 Oct 2003 20:47:47 +0100 Original-To: rms@gnu.org In-Reply-To: Original-Lines: 28 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:17581 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:17581 Richard Stallman writes: > Is HTML adequate for the job of replacing info format? Yes, it does > something vaguely similar, but that does not mean the answer is yes. > Does the HTML output produced by makeinfo give just as good results > in a browser as info files do in the info readers? Can we support > *all* the features of info just as well as we do now? I don't think that the main idea was to replace the various info readers by browsers, but to change the info format to a strict subset of HTML, and then make the info readers recognize this subset as an external format. The info readers would not need to be able to understand arbitrary HTML, just the specific HTML subset output by whatever tool was used for generating it, and native HTML browsers would not necessarily support everything the info readers could. I think the first sensible step would be to augment the HTML generating scripts in the texinfo distribution so as to include the _complete_ information available in info file format, probably as some tags usually ignored by typical HTML browsers. Once the complete information is available in the HTML files, one can write a reader for it. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum