From: "Matthias Hüning" <matthias.huening-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: changes in HTML and Slidy templates
Date: Thu, 10 Nov 2016 05:38:31 -0800 (PST) [thread overview]
Message-ID: <4f3c3b5a-1b65-42fa-a469-d78906f8a6f3@googlegroups.com> (raw)
In-Reply-To: <8a926aee-c313-47a4-892c-4059c42836fd-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 5474 bytes --]
Oops - I am sorry, I found this issue (#2221) in the changelog for 1.17.2.
(Looks like I skipped this version.)
- Matthias
Am Donnerstag, 10. November 2016 14:33:51 UTC+1 schrieb Matthias Hüning:
>
> Yes, John, I know that you are conservative about such changes (and I
> appreciate that). And of course I also fully understand that such changes
> are sometimes necessary.
>
> I usually do look at the changelog, but it's often very long and it gets
> difficult to identify those changes that might affect your own workflow.
> (Would it be doable to mark the changes that might break existing
> workflows? Give them an icon or make them red or something?)
>
> By the way:
> This specific change is not in the changelog for 1.18, isn't it? At least,
> I couldn't find it on
> https://github.com/jgm/pandoc/releases/tag/1.18
>
> Best, Matthias
>
>
> Am Donnerstag, 10. November 2016 12:24:28 UTC+1 schrieb John MacFarlane:
>>
>> Yes, I understand the concern. As you can see from my
>> reluctance to make the change, I tend to be conservative
>> about such things. And perhaps it would have been better
>> to have raised it on pandoc-discuss first.
>>
>> However, we do need to be able to make breaking changes
>> occasionally, to make pandoc better. My advice is to
>> read the changelog carefully whenever you upgrade.
>>
>> +++ Matthias Hüning [Nov 10 16 01:55 ]:
>> > Hi John,
>> > I now read issue #2221 because I wanted to understand why you made
>> this
>> > change. I saw your comment:
>> >
>> > 2) The proposed change might break some current workflows. For
>> > example, I'm accustomed to having the slide headings of my
>> > pandoc-generated reveal.js slides be h1s, and my CSS assumes that.
>> > Presumably there are others like me. Breaking changes like this
>> > should not be made lightly.
>> >
>> > While I can see the motivation for this change, I still want to let
>> you
>> > know that I share your concerns. Breaking changes can cause a lot of
>> > problems. In this case the change broke my workflow.
>> > I use the Slidy format for years now for quick and dirty
>> presentations
>> > and notes in my teaching and sometimes I change things five minutes
>> > before I have to use the slides. Fortunately, I discovered these
>> > changes when I still had time to adapt template and stylesheet, but
>> it
>> > could have been different just as well...
>> > - Matthias
>> > Am Mittwoch, 9. November 2016 18:04:07 UTC+1 schrieb John MacFarlane:
>> >
>> > +++ Matthias Hüning [Nov 09 16 07:51 ]:
>> > > Hello,
>> > > I noticed some changes in HTML en Slidy conversion in Pandoc
>> > >
>> > > HTML, EPUB, slidy, revealjs templates: Use <p> instead of
>> <h1>
>> > for
>> > > subtitle, author, date ([1]#3119). Note that, as a result of
>> > this
>> > > change, authors may need to update CSS.
>> > >
>> > > This seems to be true for html, but not for slidy, where
>> > subtitle still
>> > > is <h1>.
>> > Are you perhaps using an older version of the template?
>> > (Maybe you have one in ~/.pandoc/templates?) Template has:
>> > $if(subtitle)$
>> > <p class="subtitle">$subtitle$</p>
>> > $endif$
>> > > In Slidy, I now get <h2> for slide titles instead of <h1>,
>> isn't
>> > it?
>> > > <div id="xxx" class="slide section level2">
>> > ><h2>xxx</h2>
>> > That's this item in the changelog:
>> > + In slide shows, don't change slide title to level 1 header
>> > (#2221).
>> > You used level 2 headers in your source file, I assume?
>> >
>> > --
>> > 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 [1]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>> > To post to this group, send email to
>> > [2]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>> > To view this discussion on the web visit
>> > [3]
>> https://groups.google.com/d/msgid/pandoc-discuss/a665478a-627e-4535-
>> > bf4f-589aa2f59017%40googlegroups.com.
>> > For more options, visit [4]https://groups.google.com/d/optout.
>> >
>> >References
>> >
>> > 1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>> > 2. mailto:pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>> > 3.
>> https://groups.google.com/d/msgid/pandoc-discuss/a665478a-627e-4535-bf4f-589aa2f59017-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
>> > 4. https://groups.google.com/d/optout
>>
>>
--
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/4f3c3b5a-1b65-42fa-a469-d78906f8a6f3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 9016 bytes --]
next prev parent reply other threads:[~2016-11-10 13:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 15:51 Matthias Hüning
[not found] ` <5a35502b-7dfa-4e5c-b674-860de82cf8e0-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2016-11-09 17:04 ` John MacFarlane
[not found] ` <20161109170402.GC5951-l/d5Ua9yGnxXsXJlQylH7w@public.gmane.org>
2016-11-09 17:28 ` Matthias Hüning
2016-11-10 9:55 ` Matthias Hüning
[not found] ` <a665478a-627e-4535-bf4f-589aa2f59017-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2016-11-10 11:24 ` John MacFarlane
[not found] ` <20161110112422.GF76334-jF64zX8BO0+FMlDNSLpt5EEMvNT87kid@public.gmane.org>
2016-11-10 13:33 ` Matthias Hüning
[not found] ` <8a926aee-c313-47a4-892c-4059c42836fd-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2016-11-10 13:38 ` Matthias Hüning [this message]
2016-11-10 15:44 ` John MacFarlane
[not found] ` <20161110154400.GD7224-BKjuZOBx5Kn2N3qrpRCZGbhGAdq7xJNKhPhL2mjWHbk@public.gmane.org>
2016-11-10 16:08 ` Simon Michael
2016-11-10 15:51 ` John MacFarlane
2016-11-10 15:57 ` John MacFarlane
[not found] ` <20161110155717.GF7224-BKjuZOBx5Kn2N3qrpRCZGbhGAdq7xJNKhPhL2mjWHbk@public.gmane.org>
2016-11-10 16:44 ` Matthias Hüning
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=4f3c3b5a-1b65-42fa-a469-d78906f8a6f3@googlegroups.com \
--to=matthias.huening-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).