From: Nic Ferrier <nferrier@tapsellferrier.co.uk>
Cc: epameinondas@gmx.de, bob@rattlesnake.com, emacs-devel@gnu.org,
karl@freefriends.org
Subject: Re: A new online publishing tool for Texinfo documents.
Date: 24 Nov 2003 09:11:46 +0000 [thread overview]
Message-ID: <878ym6dtbh.fsf@kanga.tapsellferrier.co.uk> (raw)
In-Reply-To: <87znemp5a0.fsf@mail.jurta.org>
Juri Linkov <juri@jurta.org> 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.
>Currently I see at least three ways to do it:
>
> 1. continue to hack existing info.el to overcome existing limitations
> of Info format;
> 2. extend existing Web browser implemented in Emacs for better support
> of Info HTML navigation;
> 3. try to use an additional XML format in Emacs;
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.
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.
Nic
next prev parent reply other threads:[~2003-11-24 9:11 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-22 21:18 A new online publishing tool for Texinfo documents Karl Berry
2003-11-22 21:37 ` Nic Ferrier
2003-11-24 7:57 ` Juri Linkov
2003-11-24 9:11 ` Nic Ferrier [this message]
2003-11-25 4:27 ` Richard Stallman
2003-11-25 7:52 ` Juri Linkov
2003-11-25 11:21 ` Kim F. Storm
2003-11-25 10:37 ` Emacs and Javascript/XSLT (was Re: A new online publishing tool for Texinfo documents.) Nic Ferrier
2003-11-25 15:47 ` Stefan Monnier
2003-11-25 17:55 ` Juri Linkov
2003-11-24 9:43 ` XML and emacs " Nic Ferrier
2003-11-24 14:10 ` A new online publishing tool for Texinfo documents Karl Berry
2003-11-25 21:45 ` Juri Linkov
2003-11-24 16:22 ` Richard Stallman
2003-11-24 16:39 ` Nic Ferrier
2003-11-22 21:48 ` A new online publishing tool for Texinfo documents (regarding Lynx and Links) Nic Ferrier
2003-11-23 0:12 ` Alex Schroeder
-- strict thread matches above, loose matches on Subject: below --
2003-11-25 13:58 A new online publishing tool for Texinfo documents Karl Berry
[not found] <200311222102.hAML20T05380@f7.net>
2003-11-23 9:16 ` Stepan Kasal
2003-11-23 9:28 ` Miles Bader
2003-11-23 12:33 ` Stepan Kasal
2003-11-23 21:19 ` Miles Bader
2003-11-24 8:57 ` Stepan Kasal
2003-11-22 20:50 Nic Ferrier
2003-11-23 16:34 ` Richard Stallman
2003-11-23 16:56 ` Nic Ferrier
2003-11-25 18:36 ` Kevin Rodgers
2003-11-25 20:05 ` Nic Ferrier
2003-11-25 22:38 ` Kim F. Storm
2003-11-26 0:21 ` Robert J. Chassell
2003-11-26 18:37 ` Kevin Rodgers
2003-11-26 21:36 ` Robert J. Chassell
2003-12-02 18:54 ` Kevin Rodgers
2003-12-02 21:56 ` Robert J. Chassell
2003-12-03 0:42 ` Kevin Rodgers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878ym6dtbh.fsf@kanga.tapsellferrier.co.uk \
--to=nferrier@tapsellferrier.co.uk \
--cc=bob@rattlesnake.com \
--cc=emacs-devel@gnu.org \
--cc=epameinondas@gmx.de \
--cc=karl@freefriends.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.