From: karl@freefriends.org (Karl Berry)
Cc: epameinondas@gmx.de
Subject: Re: A new online publishing tool for Texinfo documents.
Date: Mon, 24 Nov 2003 09:10:22 -0500 [thread overview]
Message-ID: <200311241410.hAOEAMN11471@f7.net> (raw)
It's better not to split a XML file, because splitting it to many files
will complicate the processing of XML structure as a whole.
I agree, and I see no gain to splitting the XML since it is an
intermediate format in this scenario. But we're not writing the code,
so it's not up to us :).
But for such browsers HTML files is already good enough solution.
No, it isn't. That is the whole point of the Bob/Nic proposal. It does
not support search/index-search, which is a crucial feature.
1. continue to hack existing info.el to overcome existing limitations
of Info format;
I strongly, strongly believe that current Info format should continue to
be a text/console based format, essentially as it is now, trying to
describe only what can be done on character-based displays. I.e., as we
battered to death earlier, we might add color support, which is about
the only thing (I can think of) that consoles can do that Info can't now.
As I said, I see no point in trying to make Info format into some ersatz
HTML or XML with "logical" markup, trying to somehow allow reformatting
paragraphs and all the other things HTML does. That way lies madness.
For using the Info system with bitmapped displays, using HTML/XML, such
as Bob and Nic are proposing, seems to me to be a far superior approach.
HTML/XML will be much better at that than the Info format ever could be.
And we lose the simplicity and usefulness of current Info format if we
try to make it into XML.
2. extend existing Web browser implemented in Emacs for better support
of Info HTML navigation;
That is what Bob/Nic are proposing.
3. try to use an additional XML format in Emacs;
Again, that is what Bob/Nic are proposing -- essentially. I suppose one
could parse the XML output from Texinfo directly, but I don't think that
has any special benefits in this case. (Although GTK does it.) It
seems better to make it work with web browsers, since most everyone has
a browser installed already.
_______________________________________________
Texinfo home page: http://www.gnu.org/software/texinfo/
texinfo-pretest@texinfo.org
http://ff0.org/mailman/listinfo/texinfo-pretest
next prev reply other threads:[~2003-11-24 14:10 UTC|newest]
Thread overview: 35+ 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
2003-11-25 17:55 ` Juri Linkov
2003-11-24 9:43 ` XML and emacs " Nic Ferrier
2003-11-24 14:10 ` Karl Berry [this message]
2003-11-25 21:45 ` A new online publishing tool for Texinfo documents 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
-- strict thread matches above, loose matches on Subject: below --
2003-11-25 13:58 A new online publishing tool for Texinfo documents Karl Berry
[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-22 20:50 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 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=200311241410.hAOEAMN11471@f7.net \
--to=karl@freefriends.org \
--cc=epameinondas@gmx.de \
/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).