[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ePub support

From: Gavin Smith
Subject: Re: ePub support
Date: Sun, 15 Jul 2018 20:44:37 +0100

On Sat, Jul 14, 2018 at 8:42 PM, Borden Rhodes <address@hidden> wrote:
> I noticed in the TODO file of texinfo that there's a job for exporting
> into ePub. This would be a great feature because I've wanted to take
> things like the bash and sed manuals offline to read with me.

Have you tried downloading e.g. the bash manual from
https://www.gnu.org/software/bash/manual/ in a format you can use?

> The caveat is that makeinfo --no-headers doesn't suppress header
> generation when generating multipart HTML documentation. Whilst the
> ePub format will still technically work with the headers, it won't be
> pretty. I'm not sure whether this is a bug with --no-headers.

According to the documentation (read with "info texinfo -- --no-headers")

     Do not include menus or node separator lines in the output.

     When generating Info, this is the same as using '--plaintext',
     resulting in a simple plain text file.  Furthermore, '@setfilename'
     is ignored, and output is to standard output unless overridden with
     '-o'.  (This behavior is for backward compatibility.)

     When generating HTML, and output is split, also output navigation
     links only at the beginning of each file.  If output is not split,
     do not include navigation links at the top of each node at all.
     See Generating HTML.

The behaviour documented there is to output navigation links at the
beginning of each file.

> If I can get the right support, I can try to help the implementation.
> I don't have the time or resources to learn Perl, but I can probably
> code most into Python if someone wanted to translate into Perl. I
> could also help with the bash script to stitch the whole thing
> together.

Thanks for the offer, but as far as I am concerned, this does not seem
to be an approach that is likely to be fruitful. With the time taken
to rewrite something in Perl and integrate it with the existing Perl
code, it would likely be less work to write the thing oneself.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]