unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: A new online publishing tool for Texinfo   documents.
Date: Tue, 02 Dec 2003 17:42:58 -0700	[thread overview]
Message-ID: <3FCD3192.9050605@yahoo.com> (raw)
In-Reply-To: m1ARIV9-000UNjC@rattlesnake.com

Robert J. Chassell wrote:

>    Indeed, I was wrong: even a remote Info file accessed via ange-ftp
>    can be searched incrementally.
> 
> Are you sure it does this efficiently -- that is to say, will I be
> able to navigate through a complete `Emacs Lisp Reference Manual' in
> less than 17 seconds, or will it take me 17 minutes before my
> `Info-search' expression has got to the last node?


17 minutes to download 711 KB?  The uncompressed Info files in the
21-2.8 Emacs Lisp Reference Manual are 2,462,047 bytes; they gzip down
to 728,336 bytes.  So I think you could download, gunzip, and search
the whole thing in a reasonable amount of time.


> My understanding is that ange-ftp/tramp downloads the file or files to
> the client machine and the search is done by the client.


Correct.


>    If the goal is to make documentation available for web browsers,
>    makeinfo --html already does that.  Right?
> 
> No, `makeinfo --html' does a poor job; you cannot move around a
> document well.

Well, that's a different problem.  First make sure it's generating the

best possible HTML, then worry about extending the markup language.

-- 
Kevin Rodgers

  reply	other threads:[~2003-12-03  0:42 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
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 [this message]
  -- 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=3FCD3192.9050605@yahoo.com \
    --to=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).