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 07:57:17 +0000 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <87u14ygnmq.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 1069401632 16241 80.91.224.253 (21 Nov 2003 08:00:32 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 21 Nov 2003 08:00:32 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Fri Nov 21 09:00:29 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 1AN6DN-0002W0-00 for ; Fri, 21 Nov 2003 09:00:29 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1AN6DN-0008Rr-00 for ; Fri, 21 Nov 2003 09:00:29 +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 1AN78v-0004kG-4a for emacs-devel@quimby.gnus.org; Fri, 21 Nov 2003 03:59:57 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1AN78R-0004hh-Ol for emacs-devel@gnu.org; Fri, 21 Nov 2003 03:59:27 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1AN77v-0004KK-NV for emacs-devel@gnu.org; Fri, 21 Nov 2003 03:59:26 -0500 Original-Received: from [217.34.135.17] (helo=tf1.tapsellferrier.co.uk) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AN77v-0004Jm-2W for emacs-devel@gnu.org; Fri, 21 Nov 2003 03:58:55 -0500 Original-Received: from host217-34-135-22.in-addr.btopenworld.com ([217.34.135.22] helo=kanga.tapsellferrier.co.uk) by tf1.tapsellferrier.co.uk with esmtp (Exim 3.35 #1 (Debian)) id 1AN6AJ-00007H-00; Fri, 21 Nov 2003 07:57:19 +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 1AN6AH-0001gE-00; Fri, 21 Nov 2003 07:57:17 +0000 Original-To: bob@rattlesnake.com In-Reply-To: Original-Lines: 52 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:18012 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:18012 "Robert J. Chassell" writes: > Nic Ferrier wrote > > Method 1. > a) patch makeinfo so the XML output can be chunked. > .... > > This sounds the best in the long run. Some one should be able to take > your code in ten years time and work with it usefully, for some > purpose you never thought of. Yeah... it seems that: makeinfo --xml --split should work because one expects it to. > Method 2. > a) use a command line XSLT tool such as xsltproc (from the GNOME > libxml2 project: http://www.xmlsoft.org) to chunk AND style to HTML > the output of makeinfo --xml. > The styling would be as method 1, part c. > > How is this different from the existing `makeinfo --html' which also > does chunking and styling to HTML? > > Without knowing much about `xsltproc', the method scares me. Does > this method enable me to use keybindings in Mozilla to navigate via > regexp searching within a document that is spread over multiple files? > If so, good and I stop being scared. Indeed, then the suggestion > becomes very attractive. But if not, it is a distraction. It's different because now one can attach javascript to elements on the page whevever one needs it. The existing HTML doesn't do that, nor should it because it has an existing purpose. It's not scary - it's trivial. XSLT is very easy to read and implement. The XSLT solution isn't the end. To support regex searches some sort of webapplication IS needed as well. But XSLT is exactly the best choice for turning the Texinfo XML into something that would work with a webapp. Note that for method 1 and method 2 a webapplication would be needed, but only for regexp search. All the other tools, navigation, index lookup, etc... could be solved by javascript within the page. Nic