public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: CR <chuckr69-Wuw85uim5zDR7s880joybQ@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Pandoc not copying custom CSS file into EPUB file.
Date: Tue, 22 Aug 2017 06:47:06 -0700 (PDT)	[thread overview]
Message-ID: <53098f78-56ff-4276-8ac4-e8b5c70c2361@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1397 bytes --]

I have Pandoc v1.17.0.4.

My very first markdown file, 00intro.md, includes this YAML block: 
---
title: My title
author:
- My author
date: Various dates
---

I turn Markdown files into EPUB files using this command line in the 
Windows cmd window: 
c:\chuck\ebook\pandoc\pandoc -f 
markdown_mmd+backtick_code_blocks+yaml_metadata_block -t epub -o %outfile% 
--toc --css=style01.css 00intro.md 01.md 

After I create the epub I copy the epub to a zip file and look inside. 
The XHTML files reference "stylesheet.css" first (which is ok), then 
immediately below that they reference my custom css file "style01.css". 
"stylesheet.css" is in the root dir of the zip file, but "style01.css" is 
not in the EPUB file. 

Is this a bug? Or do I have to specify "style01.css" in a different way? 
Perhaps in my YAML block?

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/53098f78-56ff-4276-8ac4-e8b5c70c2361%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 2028 bytes --]

             reply	other threads:[~2017-08-22 13:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-22 13:47 CR [this message]
     [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

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=53098f78-56ff-4276-8ac4-e8b5c70c2361@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).