public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Thomas Chevrier <tchevri-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Pandoc #4317 side effect
Date: Tue, 27 Aug 2019 09:22:59 -0700	[thread overview]
Message-ID: <m2pnkqefx8.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <6a083675-a292-4bad-9ff4-8d834c477239-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


To summarize the issue here, which concerns a change to slide
show formats:

Prior to 2.7, versions of pandoc only put material under the "slide
level" headings on slides.  If you set slide level to 2, then
only material under level-2 headings would appear on slides,
and text under level-1 headings would not appear at all
(though level-1 headings would create "title slides" with
just the section title).

Reveal.js users consistently complained (#4317, #5237) that
this made it hard to structure reveal.js 2D slide shows, in
which it is common to have the "top" slide on each column
contain both a title and some text.

In response, I changed pandoc in 2.7 -- as the changelog says,

> Slide show formats behavior change: content under headers less
> than slide level is no longer ignored, but included in the title
> slide (for HTML slide shows) or in a slide after the title slide
> (for beamer). This change makes possible 2D reveal.js slideshows
> with content in the top slide on each stack (#4317, #5237).

The change to reveal.js has been welcomed by reveal.js users,
but the change to beamer is apparently not welcome by everyone.
The reason I made the change to both formats is because I want
slide shows to work the same no matter what output format you
use. (So you can switch from beamer to reveal.js, for example,
and the slides will look more or less the same.)

I had thought the beamer change was innocuous, since it could
be worked around by people who wanted to include content under
top-level section headings but not in the slides, e.g. by using
a filter to strip out this content.

Unfortunately, Thomas Chevrier's use case can't be handled that
way.  He wants to insert raw tex commands that (a) can't be
stripped out but (b) only work if they're outside the
'frame' environment created for a slide.  I can't think of any
workaround for this.

One possible course of action would be to revert the beamer
change while keeping the reveal.js change. This would potentially
have two bad consequences:

1) slide shows would render differently (in content, not just
form) in reveal.js and beamer.

2) this may break slide shows that were constructed using the
new behavior since 2.7 was released.

A less radical change might be to introduce special Div whose
contents get moved outside the slide itself. Anyway, comments
welcome.



  parent reply	other threads:[~2019-08-27 16:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-27 14:02 Thomas Chevrier
     [not found] ` <6a083675-a292-4bad-9ff4-8d834c477239-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-08-27 16:22   ` John MacFarlane [this message]
     [not found]     ` <m2pnkqefx8.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-08-24 17:57       ` Thomas Chevrier
     [not found]         ` <c4db2ddc-b3b0-4c62-a8bb-8a601e37dc48n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-08-24 20:00           ` John MacFarlane
     [not found]             ` <m2y2m3x1a3.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-08-25  3:54               ` Thomas Chevrier
     [not found]             ` <CAJffZrHi=PsXVgf6psA+gAaOJvw9bzuoQU_HbXnbzUtc0s+QLA@mail.gmail.com>
     [not found]               ` <CAJffZrHi=PsXVgf6psA+gAaOJvw9bzuoQU_HbXnbzUtc0s+QLA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-08-25  4:22                 ` John MacFarlane
     [not found]                   ` <m2v9h7uzgu.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-08-25 17:06                     ` Thomas Chevrier
     [not found]                       ` <73f0ad6f-f17d-424a-abe6-e8e29e9c7f2en-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-08-25 18:13                         ` John MacFarlane
     [not found]                           ` <m2h7sqvbiy.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-08-25 20:39                             ` Thomas Chevrier
     [not found]                               ` <d70cf350-f53a-4b7b-80ef-1bb1526e849fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-01-19 16:40                                 ` Paul Gesting

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=m2pnkqefx8.fsf@johnmacfarlane.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    --cc=tchevri-Re5JQEeQqe8AvxtiuMwx3w@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).