public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: pandoc and revealjs r-fit-text and r-stretch?
Date: Fri, 7 Jan 2022 10:57:01 -0500	[thread overview]
Message-ID: <7c4377d5-12cf-c663-2d48-835dc20de890@reagle.org> (raw)
In-Reply-To: <96ebec32-6e13-49f2-9fe9-bbcfbb74f47bn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

You should check out my "exemplar" markdown and revealjs deck. They demo all the features I could use (as well as documents those that I can't). And most of my (small) custom CSS is getting floating images with text working.

https://reagle.org/joseph/talks/2014/exemplar.md

https://reagle.org/joseph/talks/2014/exemplar.html

https://reagle.org/joseph/talks/_custom/reveal4js.css

Out of my outstanding issues, it looks like the next pandoc will address the first (most important) two, and the latter two do have hacks (i.e., use HTML and link the caption instead of the image).

1. r-fit-text
2. r-stretch
3. reveal fragment/iterate styles of fade-[direction]
4. when img an a link, pandoc does not create figure or figcaption

On 22-01-07 10:32, jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org wrote:
> Thanks for bringing this up. I have a long-running battle with reveal to get images to display how I want them too (mainly taking up as much space as possible without being distorted since I use it for lecture slides). Going to play with this a bit.


  parent reply	other threads:[~2022-01-07 15:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-05 21:06 Joseph Reagle
     [not found] ` <dffcab84-b283-2864-da6d-787851b6a3c3-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2022-01-06 23:14   ` John MacFarlane
2022-01-07 15:32   ` jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
     [not found]     ` <96ebec32-6e13-49f2-9fe9-bbcfbb74f47bn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-01-07 15:57       ` Joseph Reagle [this message]
     [not found]         ` <7c4377d5-12cf-c663-2d48-835dc20de890-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2022-01-07 16:50           ` jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org

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=7c4377d5-12cf-c663-2d48-835dc20de890@reagle.org \
    --to=joseph.2011-t1oy19wchswdnm+yrofe0a@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).