From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.text.pandoc/25981 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Thomas Chevrier Newsgroups: gmane.text.pandoc Subject: Re: Pandoc #4317 side effect Date: Mon, 24 Aug 2020 10:57:09 -0700 (PDT) Message-ID: References: <6a083675-a292-4bad-9ff4-8d834c477239@googlegroups.com> Reply-To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_826_763634738.1598291829320" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="12090"; mail-complaints-to="usenet@ciao.gmane.io" To: pandoc-discuss Original-X-From: pandoc-discuss+bncBCI5RYHTR4KRB5X6R75AKGQEN4IUNGQ-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Mon Aug 24 19:57:15 2020 Return-path: Envelope-to: gtp-pandoc-discuss@m.gmane-mx.org Original-Received: from mail-oo1-f58.google.com ([209.85.161.58]) by ciao.gmane.io with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1kAGiX-0002yO-OI for gtp-pandoc-discuss@m.gmane-mx.org; Mon, 24 Aug 2020 19:57:13 +0200 Original-Received: by mail-oo1-f58.google.com with SMTP id i25sf5715695ooe.14 for ; Mon, 24 Aug 2020 10:57:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20161025; h=sender:date:from:to:message-id:in-reply-to:references:subject :mime-version:x-original-sender:reply-to:precedence:mailing-list :list-id:list-post:list-help:list-archive:list-subscribe :list-unsubscribe; bh=5J4qXu99szuYXwMLP1L1VDBoSAE1RnLxToieuPbRuWE=; b=lO7e55llhLkZM+xFYlNev6cdMzOd8HiIXtcA765Qu6jR8cZ17geEcYRFfFb1EOuJ61 IW7HXeKXKEg7yBotRantTM79TUBbMIU2PJdoxmB1CjeQmwyfeJStA3iMx3cQ9zzbkjQs XN125ea3FG20dvznYkTRbqFZp4eiZK/JFi0SQahgwn+jFwcBuNEP2B1tURzKBk8HwEc2 52lwIwnu+eRgUmAwEb5sopYA57J9I6Fh0CI5Xu1Z8rMwxGiSX9RVcYE1dwg+c7ee5TzK c20sZg3Oza9rj2HA+TnmFnTNXw8d5OSdXiXQ8XKav8zQ1pLNGXjAt93u427OUtZ9AazD 7DgQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:list-subscribe:list-unsubscribe; bh=5J4qXu99szuYXwMLP1L1VDBoSAE1RnLxToieuPbRuWE=; b=dKw65Z75kIFgY32ZbuB3+fdE8iUL13Q3juYyzlLmsvKenr2DE+EXCe0K9DikjTPwCU 3uS0XMlZzgbhBAFbEXOtSkESrMLWjeol1UR/BqaBjuuZUD/9f6OHLju2JRBsRWmPFymM b2IZnZqqqp0YxtYTVtkOOJY0MErdrhYtFUXZWzsjK5IX0C0riJ7az6No49NRIo16y8By 8F2NsAImBSssqLcTuHrfd+ao9YSdergtgpLdMh2i0w0u35lnf6AIq971C7+dNVo7VYgV 5BeE7sicafdX/b4kAiM+qworzzvWWZ3cDByw7GHKRcvmHWs9YoFjeZtYQo8Gnx53m1Wo 9C8A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=sender:x-gm-message-state:date:from:to:message-id:in-reply-to :references:subject:mime-version:x-original-sender:reply-to :precedence:mailing-list:list-id:x-spam-checked-in-group:list-post :list-help:list-archive:list-subscribe:list-unsubscribe; bh=5J4qXu99szuYXwMLP1L1VDBoSAE1RnLxToieuPbRuWE=; b=WPfBSk0qbbLlE/O1OrjvzScHO9khUgNZ8+nuFOWlhY6DKbWe9GswdgouZlz/nUxCkn mqNBGTa/6G9XGuB/FcYuuMEa5lZnZX7mm6VyOrhpdrcFE/ofm3zRnLVeUF7j1vaOJejl Qedml0Tw5jhYd1nhEtnjgNi+FLrS4tHdpdkHE0DLfn8IwMXAcU0EKCKRzx2Li6gSb0hp jE8ZHliASQIeHInclxU5mYcXJpWRdNOd/rs9zG5cRg1ijX4YdU5j+MG9VT9KLBIhhw1F lRiBjVpIzhOVzauY6UM4BNYUWVJq4lpd5diOKviFBwvvRF3kOmgMxbCkkT1VOLERWxOJ bHcQ== Original-Sender: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org X-Gm-Message-State: AOAM532hglUJIhaktwQ6ER+ABkNyBXcqYX3TJTaAENAKRfVoCeNMxh7L 4XupVwEblAxeApF21S/p2OY= X-Google-Smtp-Source: ABdhPJyosTozvV+yv2Z6N28rUNE3pdVp4HbpX8twPERMFnm/AiFZpgZzt8kxp8sdzIP2a5j15nhM4w== X-Received: by 2002:a05:6830:1e71:: with SMTP id m17mr4610889otr.188.1598291832774; Mon, 24 Aug 2020 10:57:12 -0700 (PDT) X-BeenThere: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Original-Received: by 2002:aca:42c5:: with SMTP id p188ls2203860oia.3.gmail; Mon, 24 Aug 2020 10:57:10 -0700 (PDT) X-Received: by 2002:aca:cd05:: with SMTP id d5mr316818oig.138.1598291830006; Mon, 24 Aug 2020 10:57:10 -0700 (PDT) In-Reply-To: X-Original-Sender: tchevri-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org Precedence: list Mailing-list: list pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org; contact pandoc-discuss+owners-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org List-ID: X-Google-Group-Id: 1007024079513 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , Xref: news.gmane.io gmane.text.pandoc:25981 Archived-At: ------=_Part_826_763634738.1598291829320 Content-Type: multipart/alternative; boundary="----=_Part_827_1645881283.1598291829321" ------=_Part_827_1645881283.1598291829321 Content-Type: text/plain; charset="UTF-8" Hi folks, it's been exactly a year now and I am still not able to upgrade my version of Pandoc - stuck pre 2.7, because of the adverse change. Indeed, the "upgrade" for reveal.js users caused my latex beamer code to break down. I have tried multiple things without luck - I also tried a lua filter, but that did not work - no matter what, the content gets "slapped" onto a slide. As JGM suggests (was great watching him talk about Pandoc at TUG 2020 keynote address), I'd love to be able to simply be able to have content escape being slapped onto a slide - I believe that's precisely the spirit of Beamer, which uses heavily for that purpose. I also thought that was the spirit of pandoc - as you were setting in the yaml header your level for displaying on slides, but i have been clearly proven wrong. :-( One option would be to recompile pandoc without that change, but because of the bloomberg API, I am forced to be on windows, which would make this solution cumbersome at best (would be straightforward on linux though). FYI, I posted back then on SO, got only 2 upvotes and 2 bookmarks, but no answer, not even a comment :-( https://stackoverflow.com/questions/57614387/pandoc-4317-forces-content-under-title-slides-to-be-included-in-a-frame-in-pand Could anyone *please* help me? many thanks in advance thomas On Wednesday, August 28, 2019 at 12:23:15 AM UTC+8 John MacFarlane wrote: > > 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. > > > -- 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/c4db2ddc-b3b0-4c62-a8bb-8a601e37dc48n%40googlegroups.com. ------=_Part_827_1645881283.1598291829321 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hi folks,

it's been exactly a year now and I am= still not able to upgrade my version of Pandoc - stuck pre 2.7, because of= the adverse change.
Indeed, the "upgrade" for reveal.js users ca= used my latex beamer code to break down.
I have tried multiple th= ings without luck - I also tried a lua filter, but that did not work - no m= atter what, the content gets "slapped" onto a slide.
As JGM sugge= sts (was great watching him talk about Pandoc at TUG 2020 keynote address),= I'd love to be able to simply be able to have content escape being slapped= onto a slide - I believe that's precisely the spirit of Beamer, which uses= <mode> heavily for that purpose.
I also thought that was t= he spirit of pandoc - as you were setting in the yaml header your level for= displaying on slides, but i have been clearly proven wrong. :-(
= One option would be to recompile pandoc without that change, but because of= the bloomberg API, I am forced to be on windows, which would make this sol= ution cumbersome at best (would be straightforward on linux though).
<= div>
FYI, I posted back then on SO, got only 2 upvotes and 2 = bookmarks, but no answer, not even a comment :-(

Could any= one *please* help me?
many thanks in advance
thomas
=

On Wednesday, August 28, = 2019 at 12:23:15 AM UTC+8 John MacFarlane wrote:

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.


--
You received this message because you are subscribed to the Google Groups &= quot;pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to pand= oc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To view this discussion on the web visit https://groups.google.com/d= /msgid/pandoc-discuss/c4db2ddc-b3b0-4c62-a8bb-8a601e37dc48n%40googlegroups.= com.
------=_Part_827_1645881283.1598291829321-- ------=_Part_826_763634738.1598291829320--