From: Paul Eggert <eggert@cs.ucla.edu>
To: Sam Qasbah <samqasbah@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: epub version of Emacs manual (was: request for participating)
Date: Sun, 22 Dec 2019 11:14:41 -0800 [thread overview]
Message-ID: <5a687389-173f-d77b-e52e-640162fbe86c@cs.ucla.edu> (raw)
In-Reply-To: <CADOS=nZ2+sWfovat9WGMQW6CgK44ydof93YSa1MJCqQkW9jhCQ@mail.gmail.com>
On 12/22/19 9:23 AM, Sam Qasbah wrote:
> It is not a simple conversion from texi
> to epub, but a craft work of organizing and adapting the files, rewriting
> the formatting and adding a cover with a "fascinating" flavor.
Thanks for volunteering; it looks like a worthwhile thing to have. A good way to
get started would be to propose a patch to the Emacs master version, to support
an epub manual. You can do this by sending email to bug-gnu-emacs@gnu.org and
attach a patch, preferably in 'git format-patch' format; see
<https://debbugs.gnu.org/cgi/bugreport.cgi?bug=38708> for an example.
However, I worry that this would mean there would be two versions of the Emacs
manual, the main one maintained by developers in .texi format, and the epub one
which presumably would lag behind the main one. We wouldn't, for example, want
to delay an Emacs release while waiting for the epub version to catch up. Is
there some way to avoid this problem, by automating the epub version generation?
Perhaps it would be better to live with a not-quite-so-nice conversion, if the
conversion could be automated more. For ideas along those lines, please see:
https://per.bothner.com/blog/2016/texinfo-roadmap/
https://github.com/jlhg/texinfo2epub
https://github.com/ikrukov/epub
https://lists.gnu.org/archive/html/bug-texinfo/2018-07/msg00009.html
next prev parent reply other threads:[~2019-12-22 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-22 17:23 Request for partecipating in the project Sam Qasbah
2019-12-22 19:14 ` Paul Eggert [this message]
2019-12-24 4:13 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5a687389-173f-d77b-e52e-640162fbe86c@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=samqasbah@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.