From: John MACFARLANE <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Pandoc not copying custom CSS file into EPUB file.
Date: Tue, 22 Aug 2017 10:00:11 -0700 [thread overview]
Message-ID: <20170822170011.GB27659@protagoras.berkeley.edu> (raw)
In-Reply-To: <924ceab9-e2b7-47d0-9cb7-8fa1b8f7e393-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Glad you figured it out. In the upcoming pandoc 2.0
release, --epub-stylesheet is being removed, and --css
will work as you originally expected it to.
+++ CR [Aug 22 17 06:54 ]:
> It appears that for EPUB files, -css doesn't work. And I got this to
> work by using --epub-stylesheet=style01.css:
> c:\chuck\ebook\pandoc\pandoc -f
> markdown_mmd+backtick_code_blocks+yaml_metadata_block -t epub -o
> %outfile% --toc --epub-stylesheet=style01.css 00intro.md 01.md
> Someone should probably put a note under the -css option that it
> doesn't work for EPUB books and the note should say "use
> --epub-stylesheet=file.css instead".
>
> --
> 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 [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to
> [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> [3]https://groups.google.com/d/msgid/pandoc-discuss/924ceab9-e2b7-47d0-
> 9cb7-8fa1b8f7e393%40googlegroups.com.
> For more options, visit [4]https://groups.google.com/d/optout.
>
>References
>
> 1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 3. https://groups.google.com/d/msgid/pandoc-discuss/924ceab9-e2b7-47d0-9cb7-8fa1b8f7e393-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
> 4. https://groups.google.com/d/optout
prev parent reply other threads:[~2017-08-22 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 13:47 CR
[not found] ` <53098f78-56ff-4276-8ac4-e8b5c70c2361-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-22 13:54 ` CR
[not found] ` <924ceab9-e2b7-47d0-9cb7-8fa1b8f7e393-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-22 17:00 ` John MACFARLANE [this message]
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=20170822170011.GB27659@protagoras.berkeley.edu \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@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).