From: "Дилян Палаузов" <dilyan.palauzov@aegee.org>
To: Lars Ingebrigtsen <larsi@gnus.org>, Glenn Morris <rgm@gnu.org>
Cc: 32713@debbugs.gnu.org
Subject: bug#32713: Documentation in ePub format
Date: Thu, 22 Aug 2019 12:37:22 +0000 [thread overview]
Message-ID: <6abbe4f71b369e677f549ae608291a7a7c8f2888.camel@aegee.org> (raw)
In-Reply-To: <m38st06bt1.fsf@gnus.org>
Hello,
any progress in finding out, whether FSF or the emacs developers are in charge for publishing the documentation in epub
format?
Regards
Дилян
On Sun, 2019-07-14 at 14:27 +0200, Lars Ingebrigtsen wrote:
> Glenn Morris <rgm@gnu.org> writes:
>
> > > Dilyan Palauzov <Dilyan.Palauzov@aegee.org> writes:
> > >
> > > > please consider publishing the emacs documentations in .epub format.
> > > >
> > > > With https://github.com/jlhg/texinfo2epub texinfo is easily
> > > > converted into epub.
> > >
> > > That seems like a reasonable thing to do, but to make this happen, I
> > > think you have to contact the Free Software Foundation, as they are the
> > > ones making these manuals available. So I'm closing this bug report.
> >
> > ?
> > I don't know what you want the FSF to do here.
>
> I don't want the FSF to do anything, but this user wanted somebody to
> publish the manuals in .epub format. That seems like an FSF thing.
>
next prev parent reply other threads:[~2019-08-22 12:37 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 ` Дилян Палаузов [this message]
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 ` Дилян Палаузов
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=6abbe4f71b369e677f549ae608291a7a7c8f2888.camel@aegee.org \
--to=dilyan.palauzov@aegee.org \
--cc=32713@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rgm@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).