From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: [drew.adams@oracle.com: RE: cannot find :enable in Elispmanualindex] Date: Sun, 3 Jun 2007 16:55:02 -0700 Message-ID: References: <87r6osissn.fsf@jurta.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1180914991 9799 80.91.229.12 (3 Jun 2007 23:56:31 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 3 Jun 2007 23:56:31 +0000 (UTC) To: Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jun 04 01:56:30 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1Huzvx-000344-Rl for ged-emacs-devel@m.gmane.org; Mon, 04 Jun 2007 01:56:30 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Huzvx-0005K0-Hl for ged-emacs-devel@m.gmane.org; Sun, 03 Jun 2007 19:56:29 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Huzvv-0005Jv-3V for emacs-devel@gnu.org; Sun, 03 Jun 2007 19:56:27 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Huzvt-0005Jj-DF for emacs-devel@gnu.org; Sun, 03 Jun 2007 19:56:26 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Huzvt-0005Jg-9h for emacs-devel@gnu.org; Sun, 03 Jun 2007 19:56:25 -0400 Original-Received: from rgminet01.oracle.com ([148.87.113.118]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Huzvs-00074J-QH for emacs-devel@gnu.org; Sun, 03 Jun 2007 19:56:25 -0400 Original-Received: from rgmgw3.us.oracle.com (rgmgw3.us.oracle.com [138.1.186.112]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id l53NuM9f010918 for ; Sun, 3 Jun 2007 17:56:22 -0600 Original-Received: from acsmt350.oracle.com (acsmt350.oracle.com [141.146.40.150]) by rgmgw3.us.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id l53NuL92029080 for ; Sun, 3 Jun 2007 17:56:21 -0600 Original-Received: from dhcp-amer-whq-csvpn-gw3-141-144-81-137.vpn.oracle.com by acsmt350.oracle.com with ESMTP id 2770197821180914917; Sun, 03 Jun 2007 16:55:17 -0700 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <87r6osissn.fsf@jurta.org> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE X-detected-kernel: Linux 2.4-2.6 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:72171 Archived-At: > > One more thought: someone going to the trouble of writing a > > whole new viewer might as well use TexinfoML XML for its > > input, it seems to me (as Juri wrote). > > > > In principle, this might be just as good as using a subset of HTML. > > However, in practice, using a subset of HTML would allow any browser > > to display Info files. Could TexinfoML XML do that? > > `makeinfo --html' already generates output that any browser can display. > What is missing in HTML output are Info-specific semantical elements, > like references to next and previous nodes, menu items grouped to menus, > index items that can be easily extracted. I'm not suggesting this is the way to go, but I wrote a library, mkhtml.el, that built upon htmlize.el, changing all Info links into HTML hyperlinks. I still have the library, but it works only with an out-of-date version of htmlize.el (which I'm not even sure I still have). My point is that it is doable to 1) convert to HTML a la htmlize, and then 2) convert Info links (menus, xrefs, everything) to HTML links. You make a more general point, however. Things such as index lookup via `i' would have no HTML counterpart (or, rather, one might need to be developed). ECMAscript? (ugh!)