unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: Kevin Rodgers <ihs_4664@yahoo.com>, emacs-devel@gnu.org
Subject: Re: A new online publishing tool for Texinfo documents.
Date: 25 Nov 2003 23:38:20 +0100	[thread overview]
Message-ID: <m3d6bgxeeb.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <87ad6kb4ec.fsf@kanga.tapsellferrier.co.uk>

Nic Ferrier <nferrier@tapsellferrier.co.uk> writes:

> Kevin Rodgers <ihs_4664@yahoo.com> writes:
> 
> > Nic Ferrier wrote:
> > 
> > > It's an additional format to solve the specific problem of reading
> > > documentation that you don't happen to have on your local machine.
> > 
> > Why can't ange-ftp, tramp, or http-get be used to retrieve remote Info
> > files for local browsing within Emacs?
> 
> Because it would take a lot of work to alter the info reader to make
> that happen.

I doubt that it will take more work than adding XSLT and javascript
support to and otherwise enhancing emacs/w3.

> 
> And users would then be tied to emacs for doing it... 

What's wrong about that?
This is emacs-devel which is supposed to deal with emacs development!

>                                                       The current
> proposal offers at least as much flexibility as current Info
> publishing systems:
> 
> - it will be available to browsers
> - it will therefore be available to emacs
> - it will also therefore be available on the console (links)

so:

- this discussion will continue outside emacs-devel, right?

Thank you.

++kfs

  reply	other threads:[~2003-11-25 22:38 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-22 20:50 A new online publishing tool for Texinfo documents 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 [this message]
2003-11-26  0:21       ` Robert J. Chassell
2003-11-26  6:25         ` Eli Zaretskii
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
  -- strict thread matches above, loose matches on Subject: below --
2003-11-22 21:18 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-24 14:10     ` Karl Berry
2003-11-25 21:45       ` Juri Linkov
2003-11-24 16:22   ` Richard Stallman
2003-11-24 16:39     ` Nic Ferrier
     [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-25 13:58 Karl Berry

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3d6bgxeeb.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --cc=emacs-devel@gnu.org \
    --cc=ihs_4664@yahoo.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).