From: Uberslowpoke <uberslowpoke-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Can pandoc interpret content of latex environments?
Date: Sun, 18 Jun 2017 08:04:34 -0700 (PDT) [thread overview]
Message-ID: <47863819-46da-4650-a6e2-86a565894294@googlegroups.com> (raw)
In-Reply-To: <da6dd9b8-234e-49bf-996b-b7bbb3264e8b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1493 bytes --]
Found a workaround here:
https://groups.google.com/forum/#!topic/pandoc-discuss/3DP8NACzWjY
Everything works as desired. Maybe it would be good to add it to manual?
воскресенье, 18 июня 2017 г., 13:42:01 UTC+3 пользователь Uberslowpoke
написал:
>
> I have pretty same question. I use proof environment, and I want to
> interpret its content as markdown.
>
> суббота, 1 февраля 2014 г., 23:54:35 UTC+4 пользователь hff...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
> написал:
>>
>> Is there a way to have pandoc interpret the material between the begin
>> and end tags of a latex environment as markdown, not latex?
>>
>> As an alternative: Is it possible to run, say, a perl filter, calling
>> pandoc as an external command for transforming the replacement pattern,
>> e.g. from markdown to latex, in the process?
>>
>
--
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/47863819-46da-4650-a6e2-86a565894294%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 2240 bytes --]
prev parent reply other threads:[~2017-06-18 15:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-01 19:54 hffc07-Re5JQEeQqe8AvxtiuMwx3w
[not found] ` <b8d0fb1b-5207-4bdc-8aa2-fd844f6e2e5f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-06-18 10:42 ` Uberslowpoke
[not found] ` <da6dd9b8-234e-49bf-996b-b7bbb3264e8b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-06-18 15:04 ` Uberslowpoke [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=47863819-46da-4650-a6e2-86a565894294@googlegroups.com \
--to=uberslowpoke-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).