public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Markdown and LaTeX to beamer — Sections and TOC
Date: Sun, 30 Jul 2017 13:53:42 -0700	[thread overview]
Message-ID: <20170730205342.GI11715@Johns-MacBook-Pro.local> (raw)
In-Reply-To: <ecc12baf-02ba-4b18-b353-d3c441d432d1-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

Check out the user manual:
http://pandoc.org/MANUAL.html#structuring-the-slide-show
Let us know if this doesn't clarify things.

+++ Victor Sannier [Jul 29 17 02:59 ]:
>   Hi!
>   I strated using Pandoc and I noticed that the conversion to a beamer
>   presentation don't support LaTeX sections and convert them to frames,
>   subsections are converted to boxes.
>   The panda output is very different to the normal Tex one so that I
>   cannot add a table of contents.
>   Is there a solution ?
>   ---
>   LaTeX code :
>    \documentclass[]{beamer}
>    \usepackage[T1]{fontenc}
>    \usepackage[latin1]{inputenc}
>    \usepackage[frenchb]{babel}
>    \usetheme{Boadilla}
>    \title{Beamer}
>    \subtitle{Test}
>    \author{Author}
>    \date{2017}
>    \begin{document}
>     \tableofcontents
>   \section{Section}
>   \begin{frame}
>   Text
>   \end{frame}
>   \begin{frame}
>   Text
>   \end{frame}
>   \section{Section}
>   \subsection{Sous-section}
>   \begin{frame}
>   Text
>   \end{frame}
>   \subsection{Sous-section}
>   \begin{frame}
>   Text
>   \end{frame}
>    \end{document}
>   Normal output (texshop) :
>   [65f927a0-3e4f-4784-8bd0-51bac93923ec]
>   pandoc output :
>   [967ee2c7-4e4c-4b00-a543-408ed1e0fdef]
>
>   --
>   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-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To post to this group, send email to
>   [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To view this discussion on the web visit
>   [3]https://groups.google.com/d/msgid/pandoc-discuss/ecc12baf-02ba-4b18-
>   b353-d3c441d432d1%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-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   3. https://groups.google.com/d/msgid/pandoc-discuss/ecc12baf-02ba-4b18-b353-d3c441d432d1-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
>   4. https://groups.google.com/d/optout


      parent reply	other threads:[~2017-07-30 20:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-29  9:59 Victor Sannier
     [not found] ` <ecc12baf-02ba-4b18-b353-d3c441d432d1-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-07-30 20:53   ` John MacFarlane [this message]

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=20170730205342.GI11715@Johns-MacBook-Pro.local \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@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).