Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This should be a comment akin jleedev's mentioning the post on <a href="http://www.music.mcgill.ca/~sinclair/content/blog/using_markdown_for_beamer_presentations" rel="nofollow">using markdown for beamer presentations</a>, which in any case seems a little simpler (and better documented!). I was going to mention some pandoc 'filters' on bitbucket, <a href="https://bitbucket.org/mpastell/pandoc-filters" rel="nofollow">https://bitbucket.org/mpastell/pandoc-filters</a>, including one for beamer. It provides for ordinary pandoc image import syntax, for what that is worth.</p> <p>They work through Pandoc's json machinery which I don't know much about, together with the sort of transformation explained in <a href="http://johnmacfarlane.net/pandoc/scripting.html" rel="nofollow">http://johnmacfarlane.net/pandoc/scripting.html</a>. I'm not sure why the route through json is used. The effect is not that different from the perl substitutions used the in post above. In any case, this command:</p> <pre><code>pandoc -r markdown -w json deg.txt | runhaskell beamer.hs | pandoc -r json -w latex -s --template=templates/beamer.template &gt; deg.tex </code></pre> <p>seems to work fine on a very simple text divided into level one sections. -- With the one proviso, that <code>\begin{document}</code> is immediately followed by an <code>\end {frame}</code>. This may be inevitable given the extreme simplicity of the file <a href="https://bitbucket.org/mpastell/pandoc-filters/src/6cd7b8522cf5/beamer.hs" rel="nofollow">https://bitbucket.org/mpastell/pandoc-filters/src/6cd7b8522cf5/beamer.hs</a> which is much like the first example Behead.hs on the "Scripting with Pandoc" page. In any case, it is clear that you are meant to begin your markdown file with a bit of LaTeX, presumably beamer-specific. If you stick something like </p> <pre><code>\begin{frame}{\;} \center{What I did on my summer vacation} \center{Meredith Alvarez} </code></pre> <p>at the start of your markdown file, it all works fine, but I assume something more beamer-specific is intended. It could do with a little more documentation!</p> <p>The middle process, <code>runhaskell beamer.hs</code> is very slow, but it's instantaneous if you compile it and run </p> <pre><code>pandoc -r markdown -w json deg.txt | ./beamer | pandoc -r json -w latex -s --template=templates/beamer.template &gt; deg.tex </code></pre>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload