From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Nic Ferrier Newsgroups: gmane.emacs.devel Subject: Re: Changes to Texinfo DTD Date: 21 Nov 2003 08:49:51 +0000 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <87r802gl74.fsf@kanga.tapsellferrier.co.uk> References: <200310280126.h9S1Q9N16202@f7.net> <20031028105102.GA7330@dirtyweb.penguinpowered.com> <20031030104238.GA11503@dirtyweb.penguinpowered.com> <87vfps2x9r.fsf@ID-87814.user.dfncis.de> <878ymfdsx9.fsf@mail.jurta.org> <8765heixvu.fsf@kanga.tapsellferrier.co.uk> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1069415673 14045 80.91.224.253 (21 Nov 2003 11:54:33 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 21 Nov 2003 11:54:33 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Fri Nov 21 12:54:30 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 1AN9rq-0004lK-00 for ; Fri, 21 Nov 2003 12:54:30 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1AN9rq-0002JF-00 for ; Fri, 21 Nov 2003 12:54:30 +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 1ANARY-0000FI-R0 for emacs-devel@quimby.gnus.org; Fri, 21 Nov 2003 07:31:24 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1ANART-0000F5-Ml for emacs-devel@gnu.org; Fri, 21 Nov 2003 07:31:19 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1ANAQx-00009v-QD for emacs-devel@gnu.org; Fri, 21 Nov 2003 07:31:18 -0500 Original-Received: from [217.34.135.17] (helo=tf1.tapsellferrier.co.uk) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AN9ce-00048Y-Sw for emacs-devel@gnu.org; Fri, 21 Nov 2003 06:38:49 -0500 Original-Received: from [194.74.202.254] (helo=kanga.tapsellferrier.co.uk) by tf1.tapsellferrier.co.uk with esmtp (Exim 3.35 #1 (Debian)) id 1AN8f3-0000E4-00; Fri, 21 Nov 2003 10:37:14 +0000 Original-Received: from localhost ([127.0.0.1] helo=kanga.tapsellferrier.co.uk ident=nferrier) by kanga.tapsellferrier.co.uk with esmtp (Exim 3.35 #1 (Debian)) id 1AN6z9-0001hb-00; Fri, 21 Nov 2003 08:49:51 +0000 Original-To: bob@rattlesnake.com In-Reply-To: Original-Lines: 46 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:18013 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:18013 "Robert J. Chassell" writes: > Put another way, Info is designed for a fast connection between the > program doing the rendering and the file serving the Info file. But > HTML is designed for a slow connection between the program doing the > rendering and the Web server providing the HTML file. I don't really understand this. But maybe I'm not seeing it at the right level of detail. No matter, what I'm saying is that we can *easily* make an HTML representation of Texinfo which is better for people with slow network connections than the current format. The representation will operate in a Javascript/XSLT aware browser and have: - keyboard navigation - index term lookup - node sized downloads Search will also be included but only with the addition of a web application (a CGI script probably) held on the same server which is serving the Texinfo files. We can do this *because* we have the XML output and don't have to write complicated HTML rendering code, we can write simply HTML rendering code with XSLT. > Oliver said: > ... I wrote under the assumption that a small and lightweight > standalone info reader that works on a console is necessary. > > Yes, this is necessary, as one of the various display programs that > the new XML could use. You're not saying we have to write a new console info reader for XML are you? If you are saying that: why? The current info reader is fine for consoles, surely it's okay that it uses a different data format than XML or HTML? Nic