From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ivan Shmakov Newsgroups: gmane.emacs.devel Subject: Info and HTML Date: Sun, 07 Dec 2014 10:27:31 +0000 Message-ID: <87fvcrlppo.fsf_-_@violet.siamics.net> References: <20141205123549.GA29331@thyrsus.com> <87mw72lyzs.fsf@earlgrey.lan> <20141205190925.GA5067@thyrsus.com> <20141206061019.GC14890@thyrsus.com> <83ppbx1aag.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" X-Trace: ger.gmane.org 1417948102 20486 80.91.229.3 (7 Dec 2014 10:28:22 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 7 Dec 2014 10:28:22 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Dec 07 11:28:18 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XxZ4b-0005t6-Jf for ged-emacs-devel@m.gmane.org; Sun, 07 Dec 2014 11:28:17 +0100 Original-Received: from localhost ([::1]:57589 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XxZ4b-0005PN-5v for ged-emacs-devel@m.gmane.org; Sun, 07 Dec 2014 05:28:17 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54340) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XxZ4M-0005PE-5Z for emacs-devel@gnu.org; Sun, 07 Dec 2014 05:28:03 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XxZ4K-0004Eg-N1 for emacs-devel@gnu.org; Sun, 07 Dec 2014 05:28:02 -0500 Original-Received: from fely.am-1.org ([2a01:4f8:d15:1b86::2]:49964) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XxZ4K-0004D0-A0 for emacs-devel@gnu.org; Sun, 07 Dec 2014 05:28:00 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=siamics.net; s=a2013295; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date:Sender:References:Subject:To:From; bh=pLBnvO0t8O2ws49oUhtskBVuDOPmRRvSel4KBaPkeKo=; b=rR9CmBDUKacZUESa52idMCIU5pZtUNmtu1JHs84sez7AjhiZ8bn4OZY9mRqoMjOjxL2GSXUpI8ffDSDBCIGcs8Gh4BahEgUWF5rnrWq62BhUVeZm24pJWbdsjkr2Q/Q6+3Zy9NyokLmNplEFqTbzMaQRbUrLHLaVdDe4eibxlP4=; Original-Received: from [2a02:2560:6d4:26ca::1:1d] (helo=violet.siamics.net) by fely.am-1.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1XxZ3z-0003WX-1n for emacs-devel@gnu.org; Sun, 07 Dec 2014 10:27:39 +0000 Original-Received: from localhost ([::1] helo=violet.siamics.net) by violet.siamics.net with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1XxZ3r-0004a8-N4 for emacs-devel@gnu.org; Sun, 07 Dec 2014 17:27:31 +0700 Mail-Followup-To: emacs-devel@gnu.org In-Reply-To: (Richard Stallman's message of "Sun, 07 Dec 2014 04:20:07 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a01:4f8:d15:1b86::2 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:179257 Archived-At: --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable >>>>> Richard Stallman writes: [=E2=80=A6] > Using HTML instead of Info format would be a big improvement, since > HTML is more flexible and can represent a wider range of contents. > However, unless we have an HTML-based Info reader with the same handy > features that the current Info reader has (for instance, the commands > n, p, u, These commands are already implemented in EWW. They use the respective @rel attributes produced by Texinfo; for instance: $ nl -ba < www.gnu.org/software/emacs/manual/html_node/emacs/Minibuffer.htm= l=20 =E2=80=A6 40

41 Next: M-x, 42 Previous: Basic, 43 Up: Top (The eww-up-url command does not currently work due to a typo in the EWW code; see the patch MIMEd.) > m, The menu items in the Texinfo-produced HTML come with @accesskey attributes, which are, however, currently ignored by EWW: 57

    58
  • Basic Minibuffer: Basic usage of the minibuffer.=20 59
  • Minibuffer File: Entering file names with the minibuffer.=20 60
  • Minibuffer Edit: How to edit in the minibuffer.=20 Presumably, we can use one another value for the @rel attribute (menu-entry or nav-entry, perhaps?) to fill for that role. > i, This one is somewhat trickier. First of all, we need a way to point the browser to the relevant index page(s). The element would fit this purpose, although again, I know of no @rel value currently in use for this purpose. (At the very least, [1, 2] do not seem to mention anything related.) Then, on these index pages, we should somehow mark the index terms proper, for which we may again use a specific @rel value. (Say, rel=3D"index-page" and rel=3D"index-term"?) [1] http://microformats.org/wiki/existing-rel-values [2] http://microformats.org/wiki/Special:PrefixIndex/rel > SPC, This one is already bound to scroll-up-command, but I guess you mean that there should be a kind of eww-scroll-up-or-next-page command as well? > search through multiple nodes), it would also be a big step backward. It is certainly possible to walk over the structure pointed by the @rel links, but that will require the browser to retrieve (and cache) potentially the entire HTML manual. My guess is that there generally should be some kind of server-side search facility accompanying the manuals, for those having limited bandwidth. [=E2=80=A6] > To get the benefit of HTML and avoid the loss, we need > * A good way to represent a manual's info nodes in HTML, including > all their structure such that it can be extracted mechanically. > I suppose this is not very hard, if you know HTML better than I do, > and maybe it has been done already. Has it been? Unless I forgot something (which is quite likely), the above should be it. > * An HTML-based Info reader (can be done in Emacs) which implements > these commands as well as the usual HTML browsing features. > (Of course, these commands won't be available to someone using an > ordinary browser to look at the same HTML files, but that is out of > our hands.) > You could think of this as a special-purpose browser for web pages of > documentation. Even though I=E2=80=99m hardly a fan of ECMAScript-based solutions, I guess we may employ some such solution to allow for easy access to the indices at the least. The other features (or, rather, key bindings) are mostly there, thanks to @accesskey. [=E2=80=A6] --=20 FSF associate member #7257 http://boycottsystemd.org/ =E2=80=A6 3013 B6A0= 230E 334A --=-=-= Content-Type: text/plain Content-Disposition: inline --- a/lisp/net/eww.el +++ b/lisp/net/eww.el @@ -427,7 +427,7 @@ defun eww-handle-link (dom) ("start" . :start) ("home" . :home) ("contents" . :contents) - ("up" . up))))) + ("up" . :up))))) (and href where (plist-put eww-data (cdr where) href)))) --=-=-=--