From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: A new online publishing tool for Texinfo documents. Date: Tue, 25 Nov 2003 09:52:49 +0200 Organization: JURTA Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <87smkc7ulq.fsf@mail.jurta.org> References: <200311222118.hAMLI3v07843@f7.net> <87r800dr09.fsf@kanga.tapsellferrier.co.uk> <87znemp5a0.fsf@mail.jurta.org> <878ym6dtbh.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 1069747262 10680 80.91.224.253 (25 Nov 2003 08:01:02 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 25 Nov 2003 08:01:02 +0000 (UTC) Cc: epameinondas@gmx.de, bob@rattlesnake.com, emacs-devel@gnu.org, karl@freefriends.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Tue Nov 25 09:00:58 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 1AOY82-0000ok-00 for ; Tue, 25 Nov 2003 09:00:58 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1AOY82-00068y-00 for ; Tue, 25 Nov 2003 09:00:58 +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 1AOZ1S-00040N-Kx for emacs-devel@quimby.gnus.org; Tue, 25 Nov 2003 03:58:14 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1AOZ1O-000406-9y for emacs-devel@gnu.org; Tue, 25 Nov 2003 03:58:10 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1AOZ0s-0003wg-FK for emacs-devel@gnu.org; Tue, 25 Nov 2003 03:58:09 -0500 Original-Received: from [64.246.52.22] (helo=ns5.tangramltd.com) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.24) id 1AOZ0s-0003wZ-4I for emacs-devel@gnu.org; Tue, 25 Nov 2003 03:57:38 -0500 Original-Received: from 80-235-39-234-dsl.mus.estpak.ee ([80.235.39.234] helo=mail.jurta.org) by ns5.tangramltd.com with esmtp (Exim 4.20) id 1AOY3I-00029N-Fq; Tue, 25 Nov 2003 09:56:04 +0200 Original-To: Nic Ferrier In-Reply-To: <878ym6dtbh.fsf@kanga.tapsellferrier.co.uk> (Nic Ferrier's message of "24 Nov 2003 09:11:46 +0000") User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (gnu/linux) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - ns5.tangramltd.com X-AntiAbuse: Original Domain - gnu.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - jurta.org 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:18102 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:18102 Nic Ferrier writes: >> >> JavaScript is the only standard way to do browser-side programming that >> >> I know of. It may turn out that only a small subset of JavaScript is >> >> actually needed for the job, that wouldn't be as painful to add to Emacs >> >> and Lynx as the whole huge mess. >> > >> > Whatever, as you say, because Emacs is so adaptable we can achieve >> > something. It's just "what thing" which is important. >> >> JavaScript is mostly useful for web applications supposed to run in >> mainstream browsers. But for such browsers HTML files is already >> good enough solution. What is rather needed is to improve Emacs >> Info browser. > > Just to be clear. Bob Chassell and I are proposing a new system for > making Texinfo documentation available over the web. It's not a > replacement for Emacs Info mode. But it is intended that users of > Emacs web browsers will be able to view the HTML produced by the new > system. I still think that there is no need to add Javascript and XSLT engines to Emacs. The solution you propose will be useful for web browsers because they have no other extensibility mechanisms. But Emacs could handle pages received from server by using local Emacs Lisp programs. The received pages could contain some indication about their type so that Emacs will decide what functions to call to handle them. And this is much safer than to embed Emacs Lisp code on the web pages. > Personally, I see absolutely nothing wrong with current Emacs Info. I > use it an awfull lot (I use Texinfo for all my word processing tasks > and info mode for viewing all the documentation I have to write as > part of my work) as well as using Info from the console. I like the current Emacs Info too because it is fast and well suited for viewing the reference manuals. However, I want to fix some minor problems recently reported in it. > Right now, I almost never read HTML Info documents. I hope that the > new system Bob and I are talking about will change that a bit. I hope it will change that for the better ;-) -- http://www.jurta.org/emacs/