From: John MACFARLANE <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: How to control output when converting to Markdown
Date: Tue, 24 Oct 2017 09:48:15 -0700 [thread overview]
Message-ID: <20171024164815.GD90469@protagoras> (raw)
In-Reply-To: <6B751C58-AF69-4838-8381-0446D61D1061-AHfMSizzl90sTMJHDOTzqX9LOBIZ5rWg@public.gmane.org>
No, it's impossible. Pandoc makes certain choices in
rendering Markdown, and it's not configurable.
+++ Thomas Byskov Dalgaard [Oct 24 17 12:09 ]:
>Hi!
>
>Are there any ways to control how Markdown is written when Pandoc converts from a format to markdown?
>For example a list can be written like this:
>
>- this is the first item.
>- this is the second item.
>
>But if I want it to look like this:
>
>* this is the first item.
>* this is the second item.
>
>Could this be changed via templates or is it impossible?
>
>Best regards Thomas
>
>Sendt fra min Mac Mini via Apple Mail
>
>--
>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/6B751C58-AF69-4838-8381-0446D61D1061%40coolfortheblind.dk.
>For more options, visit https://groups.google.com/d/optout.
prev parent reply other threads:[~2017-10-24 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 10:09 Thomas Byskov Dalgaard
[not found] ` <6B751C58-AF69-4838-8381-0446D61D1061-AHfMSizzl90sTMJHDOTzqX9LOBIZ5rWg@public.gmane.org>
2017-10-24 16:48 ` 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=20171024164815.GD90469@protagoras \
--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).