From: "Дилян Палаузов" <dilyan.palauzov@aegee.org>
To: Eli Zaretskii <eliz@gnu.org>, rms@gnu.org
Cc: larsi@gnus.org, npostavs@gmail.com, 32713@debbugs.gnu.org
Subject: bug#32713: Documentation in ePub format
Date: Fri, 23 Aug 2019 09:16:25 +0000 [thread overview]
Message-ID: <6c8b194169fe00d8b6e24537dc00905e81e3872e.camel@aegee.org> (raw)
In-Reply-To: <83mug0b9hr.fsf@gnu.org>
Hello,
I want that https://www.gnu.org/software/emacs/manual/emacs.html lists under “The GNU Emacs manual is available in the
following formats:” also an “• ePub.” entry.
To achieve this, one can call on the document generating server
cd /git
git clone https://github.com/jlhg/texinfo2epub
cd /src/emacs-26.2/doc/emacs
/git/texinfo2epub/texinfo2epub.sh emacs.texi emacs.epub
Whether these lines are suitable within a build target, is a different question. Please do not concentrate on this
question, but rather on what is necessary to list epub under https://www.gnu.org/software/emacs/manual/emacs.html .
The next quesion would be, how can this be extendend this to other projects, like publishing epub under
https://www.gnu.org/software/gdb/documentation/ or https://www.gnu.org/software/wget/manual/ .
Regards
Дилян
On Fri, 2019-08-23 at 10:56 +0300, Eli Zaretskii wrote:
> > From: Richard Stallman <rms@gnu.org>
> > Date: Thu, 22 Aug 2019 19:36:32 -0400
> > Cc: larsi@gnus.org, Dilyan.Palauzov@aegee.org, 32713@debbugs.gnu.org
> >
> > > I think "publishing in .epub" just means adding some rules to the
> > > makefile (and maybe adding those files to the website).
> >
> > I think so too.
>
> This is certainly a valid interpretation of the request, but it isn't
> the only one, especially given the intended use of epub documents.
>
> The only person who knows for sure what was the intent is the OP, and
> I'd like to hear from him before deciding what to do with this issue.
>
> Thanks.
prev parent reply other threads:[~2019-08-23 9:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 4:56 bug#32713: Documentation in ePub format Dilyan Palauzov
2019-07-13 2:30 ` Lars Ingebrigtsen
2019-07-13 22:59 ` Richard Stallman
2019-07-14 1:34 ` Glenn Morris
2019-07-14 12:27 ` Lars Ingebrigtsen
2019-08-22 12:37 ` Дилян Палаузов
2019-08-22 12:48 ` Noam Postavsky
2019-08-22 23:36 ` Richard Stallman
2019-08-23 7:56 ` Eli Zaretskii
2019-08-23 9:16 ` Дилян Палаузов [this message]
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=6c8b194169fe00d8b6e24537dc00905e81e3872e.camel@aegee.org \
--to=dilyan.palauzov@aegee.org \
--cc=32713@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=npostavs@gmail.com \
--cc=rms@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).