From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: bob@gnu.org (Robert J. Chassell)
Cc: emacs-devel@gnu.org
Subject: Texinfo
Date: Fri, 11 Dec 2009 12:48:40 +0900 [thread overview]
Message-ID: <871vj2qig7.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <E1NIufP-0006b0-BY@fencepost.gnu.org>
Robert J. Chassell writes:
> Texinfo is not as sexy as HTML
This really isn't a problem, because as you point out people can
automatically transform to HTML. I don't know why people bring it up.
> The format of Texinfo may be old,
This is a problem for acceptance by developers, and so somewhat
important. However, it should be possible to automatically convert
(eg) reStructuredText to Texinfo as well as vice versa. (You might
have to design an appropriate dialect of reST, but it's designed for
that.)
The real problem with Texinfo, however, is that it is a markup
language whose translator is a *compiler*. This is not well suited to
online resources, whether wikis or help facilities built into
programs. Contribute a Texinfo interpreter to Python, and you might
have an attractive proposition for the Bazaar developers. But without
that, you would have to preprocess the Python source; it couldn't be
used as written (if the help strings were in Texinfo). This is a
nonstarter.
I think a better alternative would be to keep Bazaar documentation in
a dialect of reST (or other suitable structured text) and provide a
docutils writer to produce Texinfo from that.
next prev parent reply other threads:[~2009-12-11 3:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 1:51 Texinfo Robert J. Chassell
2009-12-11 3:48 ` Stephen J. Turnbull [this message]
2009-12-13 16:22 ` Texinfo Richard Stallman
2009-12-14 0:06 ` Texinfo Martin Pool
2009-12-15 13:12 ` Texinfo Richard Stallman
2009-12-15 22:09 ` Texinfo Martin Pool
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=871vj2qig7.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=bob@gnu.org \
--cc=emacs-devel@gnu.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).