From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: GNU ELPA visibility
Date: Thu, 01 Nov 2012 08:42:55 -0400 [thread overview]
Message-ID: <jwvbofhfqld.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <878valgb6v.fsf@gmail.com> (Jambunathan K.'s message of "Thu, 01 Nov 2012 10:40:48 +0530")
>> I.e. we need to replace the READMEs with more structured files which
>> can be easily turned into acceptable HTML (no need to be fancy, here)
>> as well as easy to render acceptably in Emacs (extra bonus points if
>> that same format can end up being used as a replacement for Info ;-).
> Org can be exported to HTML, Plain text (ASCII) and texi.
So far, Org, ReST, Markdown, and Texinfo sound like the best
options, indeed.
Texinfo requires an extra step (generate Info) before rendering in Emacs
but has the advantage that this rendering already exists and that
Texinfo is the standard GNU documentation format. It has its
weaknesses, but it's a tool we know (i.e. which is why we already know
its weaknesses).
I'd be interested to see some sample rendering of Markdown, Org, and ReST
both in HTML and inside Emacs, for comparison.
Stefan
next prev parent reply other threads:[~2012-11-01 12:42 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 19:30 GNU ELPA visibility Stefan Monnier
2012-10-25 20:04 ` Jeremiah Dodds
2012-10-25 20:18 ` Drew Adams
2012-10-26 7:29 ` Tassilo Horn
2012-10-27 6:33 ` Bastien
2012-10-26 4:22 ` Jambunathan K
2012-10-27 6:39 ` Bastien
2012-11-01 4:33 ` Stefan Monnier
2012-11-01 5:10 ` Jambunathan K
2012-11-01 5:13 ` chad
2012-11-01 5:18 ` Jambunathan K
2012-11-01 12:42 ` Stefan Monnier [this message]
2012-11-02 7:12 ` Daniel Hackney
2012-11-02 7:48 ` Jorgen Schaefer
-- strict thread matches above, loose matches on Subject: below --
2012-10-25 19:58 Dmitry Gutov
2012-10-25 21:10 ` Stefan Monnier
2012-10-25 21:23 Dmitry Gutov
2012-10-25 21:34 ` Drew Adams
2012-10-25 21:47 ` Dmitry Gutov
2012-10-25 21:52 ` Drew Adams
2012-10-26 1:37 ` Stefan Monnier
2012-10-25 21:48 ` Jorgen Schaefer
2012-10-25 22:14 Dmitry Gutov
2012-10-25 22:47 ` Jorgen Schaefer
2012-10-26 16:10 Dmitry Gutov
2012-10-26 18:31 ` Stefan Monnier
2012-10-26 18:53 ` chad
2012-10-26 19:11 ` Stefan Monnier
2012-10-27 5:18 ` Chong Yidong
2012-10-27 11:26 ` Dmitry Gutov
2012-10-28 16:29 Daniel Hackney
2012-10-28 16:47 ` Eli Zaretskii
2012-10-28 18:23 ` Andreas Schwab
2012-10-28 20:26 Dmitry Gutov
2012-11-02 18:47 Dmitry Gutov
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=jwvbofhfqld.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=kjambunathan@gmail.com \
/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).