From: James Kayser <james.kayser-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
Cc: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: MacOS Big Sur update breaks HTML generation
Date: Tue, 4 May 2021 16:12:35 -0400 [thread overview]
Message-ID: <CAPqHhWX9Fa2-bKJshWDhBHUw70FZkW98p6P647DqN3ShZELBMw@mail.gmail.com> (raw)
In-Reply-To: <m2pmy61jy2.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 4062 bytes --]
In an effort to make the answer more easily found for others who are also
asking the wrong questions, and looking in the wrong places. And also for
documentation purposes.
-M document-css=false
will stop pandoc from inserting CSS into the HTML header.
The long story..
An ansible script sneakily did a brew upgrade on a macOS dev machine just
prior to a big sur update. It upgraded pandoc (which had not been upgraded
in a while), then the OS got upgraded. After reboot, pandoc started
inserting CSS into the header that broke the styling. I tried to run
pandoc on a fresh install of linux mint with the latest updates and the *latest
version of pandoc* to troubleshoot. It didn't insert CSS into the header,
and the output styling was not affected. This further led me to believe
the OS update broke something. I Grabbed a new mac that also had the new
version of Big Sur, installed the latest version of pandoc, and it
generated lots of CSS that broke the styling.
So yes John, you're 100% correct that it had nothing to do with the Big Sur
update, and pandoc got upgraded. -M document-css=false proved that. Thank
you, I owe you a drink!
-James
On Tue, May 4, 2021 at 1:35 PM John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> wrote:
>
> It has nothing to do with Big Sur. Most likely you've installed
> a different version of pandoc than you were used to.
>
> So, check the changelog
> https://pandoc.org/releases.html
>
> and you'll see an announcement of some changes to the default
> CSS, as well as a way to disable it if you don't like it.
>
> The html5shiv thing has always been there; it's a way to get
> the HTML5 features to work with old IE versions, and it is just
> a harmless comment otherwise. (At this point we could probably
> remove it. IE 9 was released in 2011, and anyone using an older
> version at this point should be very strongly advised not to!)
>
> James Kayser <james.kayser-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
> > 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
> .
>
--
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/CAPqHhWX9Fa2-bKJshWDhBHUw70FZkW98p6P647DqN3ShZELBMw%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 5828 bytes --]
prev parent reply other threads:[~2021-05-04 20:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 16:57 James Kayser
[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 [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=CAPqHhWX9Fa2-bKJshWDhBHUw70FZkW98p6P647DqN3ShZELBMw@mail.gmail.com \
--to=james.kayser-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=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).