* Upgrade to pandoc 2.1 (on Win 10) causes --css option not to work (Markdown to HTML)
@ 2018-01-09 16:31 Stuart Rossiter
[not found] ` <d32738c8-dced-4119-8930-6e8fbfaa8112-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
0 siblings, 1 reply; 5+ messages in thread
From: Stuart Rossiter @ 2018-01-09 16:31 UTC (permalink / raw)
To: pandoc-discuss
[-- Attachment #1.1: Type: text/plain, Size: 1025 bytes --]
Just upgraded from 1.19 to 2.1 to get the new gfm parser, but this seems to
have caused the CSS option not to work.
Using options as below:
pandoc -f gfm-hard_line_breaks+smart --css=pandoc.css --columns=1000 -o
output.htm input.md
There is no CSS link at all in the produced HTML. The same thing happens if
I revert back to the old format I was using in 1.19 (-f
markdown_github-hard_line_breaks).
Is anyone else finding this?
Thanks,
Stuart
--
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/d32738c8-dced-4119-8930-6e8fbfaa8112%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 1596 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Upgrade to pandoc 2.1 (on Win 10) causes --css option not to work (Markdown to HTML)
[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
1 sibling, 0 replies; 5+ messages in thread
From: Stuart Rossiter @ 2018-01-09 16:45 UTC (permalink / raw)
To: pandoc-discuss
[-- Attachment #1.1: Type: text/plain, Size: 698 bytes --]
>
> Tested further:
>
-- works fine on 1.19.2.1
-- fails on 2.0, 2.0.6 and 2.1
Installed using the Windows MSI installer.
--
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/daf4b43c-9a25-486e-bcea-704cb4293782%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 1305 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Upgrade to pandoc 2.1 (on Win 10) causes --css option not to work (Markdown to HTML)
[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
[not found] ` <2cd8ea38-e9a6-4a87-8e41-6ddfcf13c541-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
1 sibling, 1 reply; 5+ messages in thread
From: Stuart Rossiter @ 2018-01-09 17:43 UTC (permalink / raw)
To: pandoc-discuss
[-- 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 --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Upgrade to pandoc 2.1 (on Win 10) causes --css option not to work (Markdown to HTML)
[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>
0 siblings, 1 reply; 5+ messages in thread
From: John MacFarlane @ 2018-01-09 17:56 UTC (permalink / raw)
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw
> 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).
Yes, it may be that --css used to imply -s but doesn't any
more? If so, I'm not sure that was intended.
> 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 can specify a title using
--metadata title="Whatever"
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Upgrade to pandoc 2.1 (on Win 10) causes --css option not to work (Markdown to HTML)
[not found] ` <20180109175603.GD43599-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
@ 2018-01-10 10:00 ` Stuart Rossiter
0 siblings, 0 replies; 5+ messages in thread
From: Stuart Rossiter @ 2018-01-10 10:00 UTC (permalink / raw)
To: pandoc-discuss
[-- Attachment #1.1: Type: text/plain, Size: 970 bytes --]
>
> Yes, it may be that --css used to imply -s but doesn't any
> more? If so, I'm not sure that was intended.
>
Makes sense. I'd just overlooked that my script (running pandoc) wasn't
using -s because it had worked before just with the --css.
> You can specify a title using
>
> --metadata title="Whatever"
>
Thanks; I'd overlooked that metadata could also be added via an option.
--
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/548be77c-60b1-45aa-a9db-ae94ad5082b3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 1737 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2018-01-10 10:00 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-01-09 16:31 Upgrade to pandoc 2.1 (on Win 10) causes --css option not to work (Markdown to HTML) 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
[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
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).