From: CR <chuckr69-Wuw85uim5zDR7s880joybQ@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Problems with EPUBs created from Markdown and Epubreader FF plugin
Date: Thu, 21 Sep 2017 04:15:10 -0700 (PDT) [thread overview]
Message-ID: <0cbff1f8-b96a-43bf-a72b-5b55fcba4178@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1406 bytes --]
I'm making some EPUB files from markdown using Pandoc 1.19.2.1. And
Epubreader is having a problem where it doesn't show the last few lines of
each chapter. (Chapter meaning a single XHTML file within the EPUB file.)
By default, Pandoc makes a new chapter/XHTML file each time it finds a
header level 1, or '#' sign at the beginning of the line, which is what I
want.
Does anyone else have any EPUBs they can send me that were made by Pandoc
from Markdown so I can test EPUBreader some more? I don't seem to have any
problems with any other EPUB reader software. It's just Epubreader, which
was recently completely rewritten for FF 54+. I also don't have problems
with any EPUBs from other sources like archive.org.
These sample EPUBs should have longer chapters where I will need to scroll
down in EPUBreader.
Thanks!
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/0cbff1f8-b96a-43bf-a72b-5b55fcba4178%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 1858 bytes --]
reply other threads:[~2017-09-21 11:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=0cbff1f8-b96a-43bf-a72b-5b55fcba4178@googlegroups.com \
--to=chuckr69-wuw85uim5zdr7s880joybq@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).