From: karl@freefriends.org (Karl Berry)
Cc: juri@jurta.org, epameinondas@gmx.de, emacs-devel@gnu.org,
nferrier@tapsellferrier.co.uk, bob@rattlesnake.com
Subject: Re: A new online publishing tool for Texinfo documents.
Date: Tue, 25 Nov 2003 08:58:59 -0500 [thread overview]
Message-ID: <200311251358.hAPDwxD15747@f7.net> (raw)
<!-- *Info-Node* next=XX prev=XX up=XX index=XX ... -->
Most of this info, at least, is already there, in every format.
into every page and let emacs info reader -- or stand-alone info
?
Once again, I believe that the emacs/standalone info readers should not
be changed to try to read html or xml or anything-else-ml. The whole
point of info format is to be preformatted and simple to handle. If you
want logical markup, use something that was designed for it. As Bob and
Nic are proposing.
next reply other threads:[~2003-11-25 13:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-25 13:58 Karl Berry [this message]
[not found] <200311222102.hAML20T05380@f7.net>
2003-11-23 9:16 ` A new online publishing tool for Texinfo documents 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
-- 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
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=200311251358.hAPDwxD15747@f7.net \
--to=karl@freefriends.org \
--cc=bob@rattlesnake.com \
--cc=emacs-devel@gnu.org \
--cc=epameinondas@gmx.de \
--cc=juri@jurta.org \
--cc=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).