From: Stuart Rossiter <stuart.p.rossiter-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Upgrade to pandoc 2.1 (on Win 10) causes --css option not to work (Markdown to HTML)
Date: Tue, 9 Jan 2018 09:43:21 -0800 (PST) [thread overview]
Message-ID: <2cd8ea38-e9a6-4a87-8e41-6ddfcf13c541@googlegroups.com> (raw)
In-Reply-To: <d32738c8-dced-4119-8930-6e8fbfaa8112-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1195 bytes --]
Ah, OK it was because I wasn't using -s previously (but somehow in 1.19 it
always created standalone HTML pages with a <head> block).
I do then get warnings about missing metadata title and subtitle which I
understand, but (as in the documentation) gfm doesn't support the
pandoc/YAML title block extensions:
http://pandoc.org/MANUAL.html#markdown-variants.
So there seems no way of specifying a title with gfm to HTML (unless maybe
I can use HTML snippets in my Markdown which is a bit horrible). I have to
fall back to the default use-Markdown-filename-as-the-title.
Is there a known/better workaround for this?
--
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/2cd8ea38-e9a6-4a87-8e41-6ddfcf13c541%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 1687 bytes --]
next prev parent reply other threads:[~2018-01-09 17:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 16:31 Stuart Rossiter
[not found] ` <d32738c8-dced-4119-8930-6e8fbfaa8112-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-01-09 16:45 ` Stuart Rossiter
2018-01-09 17:43 ` Stuart Rossiter [this message]
[not found] ` <2cd8ea38-e9a6-4a87-8e41-6ddfcf13c541-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-01-09 17:56 ` John MacFarlane
[not found] ` <20180109175603.GD43599-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2018-01-10 10:00 ` Stuart Rossiter
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=2cd8ea38-e9a6-4a87-8e41-6ddfcf13c541@googlegroups.com \
--to=stuart.p.rossiter-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).