public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: EPUB files crash my e-book reader
Date: Thu, 29 Apr 2021 14:07:13 +0200	[thread overview]
Message-ID: <87lf91e1la.fsf@zeitkraut.de> (raw)
In-Reply-To: <6056bed7-8403-6397-dbba-363889d433f8-GANU6spQydw@public.gmane.org>

The only thing I can think of is to try and use EPUB2 instead of EPUB3.
Maybe the reader doesn't like some EPUB3 feature that's triggered by
these websites? Try this:

    pandoc -o mypage.epub -t epub2 mypage.html

HTH,
Albert

Gilles <codecomplete-GANU6spQydw@public.gmane.org> writes:

> Hello,
>
> I used the following commands to turn a couple of web pages into EPUB to read on
> my no-name reader:
>
> wget -O mypage.html http://www.acme.com/somepage.html
> pandoc.2.9.2.1.exe -o mypage.epub mypage.html
>
> (Until I gather the courage of installing a new, 64-bit computer and
> re-installing all my stuff, that is the most recent release of Pando I can use
> because I'm still running 32-bit Windows7.)
>
> For some reason, those two URLs freeze my reader after turning them into EPUB
> files, although they open fin in Windows using SumatraPDF :
>
> https://www.vox.com/22346085/covid-19-vietnam-response-travel-restrictions
> https://www.vox.com/22380161/south-korea-covid-19-coronavirus-pandemic-contact-tracing-testing
>
> I haven't experienced that with other files, be they EPUB or PDF.
>
> Any idea what I could try in the meantime ?
>
> Thank you.


--
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe  e836 388d c0b2 1f63 1124


  parent reply	other threads:[~2021-04-29 12:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29  9:17 Gilles
     [not found] ` <6056bed7-8403-6397-dbba-363889d433f8-GANU6spQydw@public.gmane.org>
2021-04-29 12:07   ` Albert Krewinkel [this message]
     [not found]     ` <87lf91e1la.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2021-04-29 12:24       ` Gilles
2021-04-29 16:01   ` dmccunney

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=87lf91e1la.fsf@zeitkraut.de \
    --to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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.
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 NNTP newsgroup(s).