From: Daniel Staal <DStaal-Jdbf3xiKgS8@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Markdown to PDF via TeX: Tyring to change section title color
Date: Mon, 17 May 2021 17:13:01 -0400 [thread overview]
Message-ID: <8f84d4f0-42a9-4375-7e20-1b95a8195d55@usa.net> (raw)
In-Reply-To: <47556979-9357-c3d3-b3ed-a3031a195127-EkmVulN54Sk@public.gmane.org>
On 5/15/21 10:14 PM, Randy Yates wrote:
> So this brings me to the following important question: when using pandoc
> to convert from markdown input to markdown output, is the markdown
> output "standard" markdown with all the pandoc-specific extenions
> implemented as native markdown? If so, that would work with our doxygen
> flow.
The default output would be with all/most of the pandoc-specific
extensions enabled. So by default I wouldn't expect it to work with
doxygen directly. (At least, you'll get some markup text getting passed
through.)
However, Pandoc uses named extensions for all or nearly all of it's
extensions, and they can be enabled/disabled on an individual basis. It
also has direct support for several Markdown variants, so if doxygen
directly supports say Github's Markdown, you can tell Pandoc to only
export that. (One of those variants being the original base Markdown.)
So you may want to tweak a bit to get the best support, but generally
Pandoc should be tweakable to get what you need.
Daniel T. Staal
--
---------------------------------------------------------------
This email copyright the author. Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes. This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---------------------------------------------------------------
prev parent reply other threads:[~2021-05-17 21:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AQHXSQcwDnbVHcAVt0CyTplqbe+TqKrkBQMAgAAhy3A=>
2021-05-14 21:22 ` rurq...-Zl5T1cyB3pc@public.gmane.org
[not found] ` <c487e498-4249-4800-ab99-0e3dc9fca664n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-15 7:31 ` gnpan
[not found] ` <8d49ee0f-a978-4cac-9df0-6f0fcb2b6369n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-15 7:34 ` AW: " denis.maier-FfwAq0itz3ofv37vnLkPlQ
[not found] ` <d32560495cc7456bbb78e302aaff271f-FfwAq0itz3ofv37vnLkPlQ@public.gmane.org>
2021-05-15 16:06 ` 'russurquhart1' via pandoc-discuss
[not found] ` <37ef69ff-8fd6-4092-9291-bd7a2515b679n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-15 16:38 ` gnpan
2021-05-15 18:50 ` Randy Yates
[not found] ` <f025f0e7-98ff-4f50-9ba2-37687041fb3dn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-16 0:12 ` John MacFarlane
[not found] ` <m2eee7mt98.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2021-05-16 2:14 ` Randy Yates
[not found] ` <47556979-9357-c3d3-b3ed-a3031a195127-EkmVulN54Sk@public.gmane.org>
2021-05-17 12:39 ` Russ Urquhart
2021-05-17 21:13 ` Daniel Staal [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=8f84d4f0-42a9-4375-7e20-1b95a8195d55@usa.net \
--to=dstaal-jdbf3xikgs8@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).