From: Seri <seritrinh-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Create ePub from Markdown with Pandoc API
Date: Wed, 19 Nov 2014 23:09:51 -0800 (PST) [thread overview]
Message-ID: <c5f0ab8a-3fd6-4b03-9bdb-4b51b6c376c0@googlegroups.com> (raw)
In-Reply-To: <26b25b1e-7f3e-4738-aafc-a627c37b6510-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 964 bytes --]
I managed to make a little progress. I can confirm that `readMarkdown def`
works just fine since the resulting Pandoc does contain everything.
However, when it is fed into `writeEPUB def`, the content (the `Para`
elements in Pandoc format) is somehow lost. The resulting EPUB looks like
this:
Chapter One
Chapter Two
I have tried different `WriterOptions` but still did not succeed.
--
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/c5f0ab8a-3fd6-4b03-9bdb-4b51b6c376c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 1787 bytes --]
next prev parent reply other threads:[~2014-11-20 7:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 5:26 Seri
[not found] ` <26b25b1e-7f3e-4738-aafc-a627c37b6510-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2014-11-20 7:09 ` Seri [this message]
[not found] ` <c5f0ab8a-3fd6-4b03-9bdb-4b51b6c376c0-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2014-11-20 17:27 ` John MacFarlane
[not found] ` <20141120172705.GB91479-bi+AKbBUZKbivNSvqvJHCtPlBySK3R6THiGdP5j34PU@public.gmane.org>
2014-11-21 7:04 ` Seri
[not found] ` <a2ba29af-cbb1-4cf2-aca0-88f94ddd3888-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2014-11-21 18:02 ` John MacFarlane
[not found] ` <20141121180250.GE97029-bi+AKbBUZKbivNSvqvJHCtPlBySK3R6THiGdP5j34PU@public.gmane.org>
2014-11-22 6:21 ` Seri
[not found] ` <4c8b83d5-fee2-4e47-9bbb-5b65ffd5c201-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2014-11-22 6:46 ` John MacFarlane
[not found] ` <20141122064618.GB3283-bi+AKbBUZKbivNSvqvJHCtPlBySK3R6THiGdP5j34PU@public.gmane.org>
2014-11-22 7:40 ` Seri
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=c5f0ab8a-3fd6-4b03-9bdb-4b51b6c376c0@googlegroups.com \
--to=seritrinh-re5jqeeqqe8avxtiumwx3w@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).