From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: karl@freefriends.org (Karl Berry) Newsgroups: gmane.emacs.devel Subject: Re: [drew.adams@oracle.com: RE: cannot find :enable in Elisp manualindex] Date: Tue, 5 Jun 2007 19:32:39 -0500 Message-ID: <200706060032.l560WdC20963@f7.net> References: NNTP-Posting-Host: lo.gmane.org X-Trace: sea.gmane.org 1181089972 23183 80.91.229.12 (6 Jun 2007 00:32:52 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 6 Jun 2007 00:32:52 +0000 (UTC) To: rms@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 06 02:32:50 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 1HvjSC-0005ga-6W for ged-emacs-devel@m.gmane.org; Wed, 06 Jun 2007 02:32:48 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HvjSB-0007ka-Ff for ged-emacs-devel@m.gmane.org; Tue, 05 Jun 2007 20:32:47 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HvjS7-0007kU-IK for emacs-devel@gnu.org; Tue, 05 Jun 2007 20:32:43 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HvjS5-0007jI-49 for emacs-devel@gnu.org; Tue, 05 Jun 2007 20:32:42 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HvjS4-0007jF-VP for emacs-devel@gnu.org; Tue, 05 Jun 2007 20:32:40 -0400 Original-Received: from server1.f7.net ([64.34.169.74] helo=f7.net) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HvjS3-0003Oo-Sq; Tue, 05 Jun 2007 20:32:40 -0400 X-Envelope-From: karl@freefriends.org X-Envelope-To: rms@gnu.org Original-Received: (from karl@localhost) by f7.net (8.11.7-20030920/8.11.7) id l560WdC20963; Tue, 5 Jun 2007 19:32:39 -0500 In-Reply-To: X-detected-kernel: Linux 2.6, seldom 2.4 (older, 4) 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:72303 Archived-At: I wonder if there is a clean and simple way to implement these features (menus and indices) with valid "ordinary" HTML, They are. They are lists of links. As in:
  • Menu item ... (Of course there are lots of details, but that's the basic idea.) and label that valid HTML as "menu" or "index" using `div', Right now they have classes specified in the
      element:
        ...
        ...
      If it's desirable to use
      for some reason, that's obviously easy to do. However, in practice, using a subset of HTML would allow any browser to display Info files. Could TexinfoML XML do that? I'm not sure. It is possible to associate "style information", at least, with an XML schema that a browser would see, but whether that is enough to do a good job, I've never investigated. Maybe someone would like to do that. Using the HTML output vs. using the TexinfoML output are quite different approaches. Which one is better depends on how much of the rendering you want to control in Emacs. If you want complete control, then it would make sense to use TexinfoML, whose goal is basically to be an XML transliteration of the input. The HTML (or XHTML) output is more of a "processed form" similar in spirit to Info -- although it is certainly possible to affect the look of the HTML output at HTML-rendering time, there are more limits than in the XML approach. As an example, consider the HTML for a node, which starts a paragraph, includes the next/prev pointers as text, defines anchors to make cross-references work, and so on:

      Next: , Up: Terminal Input/Output
      Compare that with the TexinfoML XML, which merely declares what the various components are and says nothing about how they are displayed: \typein \typeout Terminal Input/Output ... Hope this helps, karl