unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nic Ferrier <nferrier@tapsellferrier.co.uk>
Subject: A new online publishing tool for Texinfo documents.
Date: 22 Nov 2003 20:50:39 +0000	[thread overview]
Message-ID: <8765hcf7q8.fsf@kanga.tapsellferrier.co.uk> (raw)

Bob Chasell and I have been discussing a new way of making Texinfo
available online. I am planning to build what we have discussed over
December.

This message has been sent to all interested parties.

The aims of the new system are to make a web based info reader that
would be as good as the console based Info reader and that can be
used by people with slow Internet connections and free software web
browsers (Mozilla, Galeon, etc... as well as Emacs/W3, Lynx, etc...)


Our plan is to do this:

1 alter makeinfo --xml so that it splits the XML by Texinfo
  nodes. The --no-split switch will cause the existing output (or
  maybe add a new switch for the new XML output?)

2 write an XSLT stylesheet that transforms the chunked XML into
  specialized HTML;

  the specialized HTML will include Javascript to emulate Info
  navigation, index lookups, etc...

3 write a CGI script that will lookup a regular expression in the HTML
  files and return either a list of hits or the HTML file containing
  the Nth hit (N being an optional argument supplied to the CGI
  script)

4 write a shell script for linking all this together, and possibly to
  auto-magically install the produced files into an Apache webserver
  (other webservers to be supported as and when I have time).


The shell script(4) will be dependant on a tool called xsltproc which
comes with the GNOME libxsl library and is quite commonly available
on free software machines. xsltproc runs on all free operating
systems and also some non-free ones such as Windoze (but obviously we
don't care much about those  /8-)



I personally don't think this will deprecate the existing HTML output
from makeinfo because that has good support for ALL browsers.



There is one big problem with the current plan:

Emacs/W3 and Lynx do not support Javascript so we will have to find
another way of binding actions to keys within the HTML pages
downloaded to those browsers.

Does anyone have any bright ideas about that?


I am considering the potential of adding Mozilla's Javascript engine
to Emacs and Lynx which would solve this problem. The licence of
Mozilla's Javascript engine is compatible with the GPL. However, I
think this might be rather a big job, certainly bigger than the new
publishing system for online Texinfo.

 
On the subject of Lynx, has anyone tried this version of Links?

  http://atrey.karlin.mff.cuni.cz/~clock/twibright/links/

It apparently has Javascript support and is GPLed.


Nic

             reply	other threads:[~2003-11-22 20:50 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-22 20:50 Nic Ferrier [this message]
2003-11-23 16:34 ` A new online publishing tool for Texinfo documents 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
  -- 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=8765hcf7q8.fsf@kanga.tapsellferrier.co.uk \
    --to=nferrier@tapsellferrier.co.uk \
    /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).