From: Julius Pfrommer <julius.pfrommer@kit.edu>
To: <emacs-devel@gnu.org>, <jwiegley@gmail.com>
Subject: Re: Improving the presentation of Emacs user documentation
Date: Wed, 10 Feb 2016 12:18:29 +0100 [thread overview]
Message-ID: <20160210121829.000005c2@kit.edu> (raw)
John Wiegley:
> Awesome. Feel free to dig into texi2html, plus better CSS. Double
> bonus if it looks great in eww and on mobile.
There may be a low-cost solution with almost equal results.
Many projects use Sphinx [1] to render their documentation to html.
The look-and-feel of the generated html is selected via themes. Some of
the themes look very similar to the spacemacs example [2].
Somebody already wrote a tool that converts the GCC texinfo
documentation to rst (restructured text), that can then be fed into
Sphinx:
https://gcc.gnu.org/ml/gcc-patches/2015-11/msg01030.html
Depending on the maturity of the conversion, this could be an
alternative build chain to render the documentation to html without
changing the input format. Also, Sphinx can generate good-looking PDFs
and more formats.
[1] http://www.sphinx-doc.org/en/stable/
[2] http://read-the-docs.readthedocs.org/en/latest/theme.html
next reply other threads:[~2016-02-10 11:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 11:18 Julius Pfrommer [this message]
2016-02-11 18:17 ` Improving the presentation of Emacs user documentation Richard Stallman
2016-02-11 18:23 ` Marcin Borkowski
2016-02-11 21:12 ` Eli Zaretskii
2016-02-12 12:34 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2016-02-07 23:19 John Wiegley
2016-02-08 2:49 ` Xue Fuqiao
2016-02-08 2:55 ` Xue Fuqiao
2016-02-08 8:22 ` Andreas Röhler
2016-02-08 13:02 ` Richard Stallman
2016-02-08 13:12 ` Nicolas Petton
2016-02-08 14:27 ` Stefan Monnier
2016-02-08 16:00 ` John Wiegley
2016-02-08 16:22 ` Drew Adams
2016-02-08 16:43 ` Marcin Borkowski
2016-02-08 16:44 ` Marcin Borkowski
2016-02-08 16:55 ` Nicolas Petton
2016-02-08 17:04 ` Drew Adams
2016-02-08 16:54 ` Nicolas Petton
2016-02-09 12:13 ` Richard Stallman
2016-02-09 13:16 ` Nicolas Petton
2016-02-08 14:23 ` Stefan Monnier
2016-02-08 14:34 ` Andreas Schwab
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=20160210121829.000005c2@kit.edu \
--to=julius.pfrommer@kit.edu \
--cc=emacs-devel@gnu.org \
--cc=jwiegley@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).