From: BJ <bjoern.lippert-aoCR0UM+3MJWk0Htik3J/w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Tell pandoc to respect rst in markdown files while transforming to rst
Date: Tue, 18 Aug 2020 00:22:26 -0700 (PDT) [thread overview]
Message-ID: <ba94e3c9-2f4b-4a5a-bd3b-4f6886aee523n@googlegroups.com> (raw)
In-Reply-To: <m2eeo9jdpv.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1548 bytes --]
Sorry for contacting you personally. I answered via my email client before.
I hope I did it correct now.
Yes you are right, thanks. This kind of conversion works.
https://pandoc.org/try/?text=%23+markdown%0A%0A%60%60%60%7B%3Drst%7D%0A%60this+is+rst%60_%0A%60%60%60%0A&from=markdown&to=rst&standalone=0
If using Github flavoured markdown as source format, it will look
differently... I will do some more investigation on my side, to find out,
which better fits my needs.
Thanks so far!
On Friday, August 14, 2020 at 8:15:58 PM UTC+2 John MacFarlane wrote:
>
> > How to tell pandoc while transforming the RST-enriched markdown to RST
> to
> > keep this indention? It seems pandoc removes (left trim) without mercy.
> Is
> > there a toggle or plugin I missed? Or could I add some magic-markup in
> the
> > source markdown?
>
> Well, that's very easy, if you're using pandoc's markdown
> extensions. Just use a "raw attribute":
>
> ```{=rst}
> .. note::
>
> .. include:: /path/to/file
>
> Some static text also with RST-valid indention
> ```
>
> This will be passed verbatim to RST output and ignored for other
> formats.
>
>
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/ba94e3c9-2f4b-4a5a-bd3b-4f6886aee523n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2387 bytes --]
next prev parent reply other threads:[~2020-08-18 7:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 14:58 BJ
[not found] ` <d88ec922-7c61-4cbe-8599-b435540c6a9bn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-08-14 18:15 ` John MacFarlane
[not found] ` <m2eeo9jdpv.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-08-18 7:22 ` BJ [this message]
[not found] ` <ba94e3c9-2f4b-4a5a-bd3b-4f6886aee523n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-08-21 18:51 ` John MacFarlane
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=ba94e3c9-2f4b-4a5a-bd3b-4f6886aee523n@googlegroups.com \
--to=bjoern.lippert-aocr0um+3mjwk0htik3j/w@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).