From: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Juri Linkov <juri@jurta.org>,
emacs-devel@gnu.org, "Kim F. Storm" <storm@cua.dk>
Subject: Re: Emacs and Javascript/XSLT (was Re: A new online publishing tool for Texinfo documents.)
Date: 25 Nov 2003 10:47:27 -0500 [thread overview]
Message-ID: <jwv4qwssb8r.fsf-monnier+emacs/devel@vor.iro.umontreal.ca> (raw)
In-Reply-To: <87u14sbup3.fsf_-_@kanga.tapsellferrier.co.uk>
> Whether the new publishing system relies on Javascript/XSLT or not is
> aside from the question of whether Javascript/XSLT functionality
> should be added to Emacs/W3. Clearly, Emacs/W3 is never going to be a
> competitive browser without those features.
Emacs/W3 has been dying for the last several years, so its competitivity
currently depends on much more serious issues than "how does it deal with
Javascript and XSLT". The first issue is "who is going to work on it".
Stefan
next prev parent reply other threads:[~2003-11-25 15:47 UTC|newest]
Thread overview: 17+ 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
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 [this message]
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
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=jwv4qwssb8r.fsf-monnier+emacs/devel@vor.iro.umontreal.ca \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=storm@cua.dk \
/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.