From: Eli Zaretskii <eliz@elta.co.il>
Cc: texinfo-pretest@texinfo.org
Subject: Re: Re: A new online publishing tool for Texinfo documents.
Date: 26 Nov 2003 08:25:31 +0200 [thread overview]
Message-ID: <usmkbwsro.fsf@elta.co.il> (raw)
In-Reply-To: <m1AOnQt-000UNaC@rattlesnake.com> (bob@rattlesnake.com)
> Date: Tue, 25 Nov 2003 19:21:27 -0500 (EST)
> From: "Robert J. Chassell" <bob@rattlesnake.com>
>
> The Info system could be enhanced to do the same -- at least, I think
> so. Can anyone think why, if some of the work were done by the the
> device that provides the Info document, you could not run Info
> remotely over a slow connection between its rendering engine and the
> source of the Info document?
I don't see any problem in principle, except that the rendering engine
of the Info reader will have to be redesigned to work on output from
some external program that delivers small portions of the displayed
text, instead of loading the entire file into memory and working from
there.
We will also have to design some protocol between the local and
remote parts, or teach Info to use some existing protocol, to pass
requests to the remote.
_______________________________________________
Texinfo home page: http://www.gnu.org/software/texinfo/
texinfo-pretest@texinfo.org
http://ff0.org/mailman/listinfo/texinfo-pretest
next prev parent reply other threads:[~2003-11-26 6:25 UTC|newest]
Thread overview: 13+ 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 [this message]
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
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=usmkbwsro.fsf@elta.co.il \
--to=eliz@elta.co.il \
--cc=texinfo-pretest@texinfo.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 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).