From: jdh246-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: pandoc markdown inside latex environment
Date: Thu, 3 Jan 2019 22:57:49 -0800 (PST) [thread overview]
Message-ID: <1f718f07-3b7d-41d9-9826-c31aae39b72a@googlegroups.com> (raw)
In-Reply-To: <04f37530-2688-4a0d-b092-7d18f90d3631-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1570 bytes --]
Perfect, that works!
Thank you very much!
On Thursday, January 3, 2019 at 7:43:31 PM UTC-8, jdh...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org wrote:
>
> I'm using pandoc to be converted to LaTeX and in a few cases I enter raw
> latex code, which is great, since pandoc just passes it through.
> However, it seems that when it comes across a \begin macro, starting an
> environment, pandoc thinks everything in the environment is raw LaTeX and
> stops converting.
>
> Some *italics* text.
> \begin{center}
> Some centered *italics* text.
> \end{center}
>
> Becomes in the LaTeX output:
>
> Some \emph{italics} text.
> \begin{center}
> Some centered *italics* text.
> \end{center}
>
> When I'm hoping for is to convert the markdown inside the center
> environment too, like so:
>
> Some \emph{italics} text.
> \begin{center}
> Some centered \emph{italics} text.
> \end{center}
>
> Any help, suggestions for a workaround, or alternative solutions would be
> highly appreciated.
>
> - Jan
>
--
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/1f718f07-3b7d-41d9-9826-c31aae39b72a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 2448 bytes --]
prev parent reply other threads:[~2019-01-04 6:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 3:43 jdh246-Re5JQEeQqe8AvxtiuMwx3w
[not found] ` <04f37530-2688-4a0d-b092-7d18f90d3631-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-01-04 6:14 ` John MacFarlane
2019-01-04 6:57 ` jdh246-Re5JQEeQqe8AvxtiuMwx3w [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=1f718f07-3b7d-41d9-9826-c31aae39b72a@googlegroups.com \
--to=jdh246-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).