From: James Kayser <james.kayser-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: MacOS Big Sur update breaks HTML generation
Date: Tue, 4 May 2021 09:57:43 -0700 (PDT) [thread overview]
Message-ID: <32ca13a2-ae66-4157-9a3f-3a8546b9e5b8n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1531 bytes --]
I use Pandoc to convert a markdown table into a standalone HTML, but also
merge it with some HTML using the -B option. A recent update to MacOS Big
Sur causes pandoc to add additional, unwanted CSS information in the <head>
section that throws off the formatting, as well as this comment at the end.
<!--[if lt IE 9]>
<script
src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
This did not occur prior to the MacOS update, and this does not occur in a
Debian/Ubuntu based linux distribution. Only macOS Big Sur (so far that
I've found in my limited testing) seems to be affected.
Manually deleting the excess information in the head corrects the
formatting, but I cannot figure out a way to have pandoc not put it in
there. I've tried using the -B -H, but it keeps putting it in there above
my CSS formatting. I even tried changing my default browser in the OS
settings to see if that corrected it, since it seems like maybe its
detecting IE9? I dunno. Does anyone know how to fix? Been at this for a
couple of days now.
Thanks,
James
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/32ca13a2-ae66-4157-9a3f-3a8546b9e5b8n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2025 bytes --]
next reply other threads:[~2021-05-04 16:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 16:57 James Kayser [this message]
[not found] ` <32ca13a2-ae66-4157-9a3f-3a8546b9e5b8n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-04 17:35 ` John MacFarlane
[not found] ` <m2pmy61jy2.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2021-05-04 20:12 ` James Kayser
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=32ca13a2-ae66-4157-9a3f-3a8546b9e5b8n@googlegroups.com \
--to=james.kayser-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).