public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Russ Urquhart <rurquhart-Zl5T1cyB3pc@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Cc: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
Subject: Re: Markdown to PDF via TeX: Tyring to change section title color
Date: Mon, 17 May 2021 07:39:05 -0500	[thread overview]
Message-ID: <CAH=xdFt=vJVmJgn9P7hboWa1ExCWVbWrqU5qvZ3Ko8YY2T=YEw@mail.gmail.com> (raw)
In-Reply-To: <47556979-9357-c3d3-b3ed-a3031a195127-EkmVulN54Sk@public.gmane.org>

Hi All,

Thanks for all the help! I finally got titlesec installed, what hoops
you have to be aware of!

To answer the question of why use Markdown to go to PDF via LaTeX when
LaTex is more expressive. I completely understand that. Our tech doc
group, using a Docs as Code workflow, already has their documentation,
initially contributed by development, in Markdown. (To my way of
thinking, going to Asciidoc would solve most of our problems of
Including files and generating PDF's directly, but you have to work
with what you have.)

I feel more confident that we'll be able to get where we want to go,
just may have to dig into TeX/LaTex a little more!

Thanks,

Russ

On Sat, May 15, 2021 at 9:14 PM Randy Yates <yates-EkmVulN54Sk@public.gmane.org> wrote:
>
> John,
>
> First of all, no matter what approach, let me thank you for such a
> powerful and wonderful tool.
>
> Regarding your TUG talk on youtube, the problem with using markdown as
> the source document for our documentation flow is that we use the
> markdown as input to doxygen to generate our final doxygen (html)
> output, and AFAIK doxygen does not honor any of the special
> pandoc-specific extensions to markdown.
>
> 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.
>
> I am still not on-board with the idea that markdown is the ideal or best
> input language, but having options is always better than the old days.
>
> --Randy
>
> On 5/15/21 8:12 PM, John MacFarlane wrote:
> > Randy Yates <yates-EkmVulN54Sk@public.gmane.org> writes:
> >
> >> Don't use markdown as your source document format. Latex's capabilities for
> >> generating rich output are far, far greater than markdown,
> > This is true.
> >
> >> which can't even generate numbered section headers.
> > It can.  pandoc -f markdown --number-sections
> >
> >>     1. Elegant mathematics
> > Also accessible from within pandoc markdown, which allows you
> > to use tex math and even macros.
> >
> >>     2. An extensive bibliography/citation system
> > Pandoc's markdown has one too (see Citations in the user's guide and pandoc --citeproc).
> >
> >>     3. The ability to natively generate graphics using Tikz/Pgm.
> > This can be done in pandoc markdown using a filter: https://github.com/pandoc/lua-filters/tree/master/diagram-generator
> >
> > Although it's true that LaTeX is more expressive and more powerful
> > than markdown, but many users may find that pandoc's extended
> > markdown has all the power they need.  In addition, there are
> > advantages to writing in this more limited format, especially
> > if you may need to target output formats other than PDF.
> > I discuss this in my TUG 2020 talk "Pandoc for TeXnicians":
> > video: https://www.youtube.com/watch?v=T9uZJFO54iM
> > slides: https://johnmacfarlane.net/tug-2020-pandoc-for-texnicians.pdf
> >
> >> So in general, choose a source document format that's the least "lossy" in
> >> terms of typographical capability, then translation to other formats incurs
> >> the least loss possible.
> > Conversions from LaTeX to other formats are notorious for being
> > lossy -- precisely *because* of the expressiveness of LaTeX.  I
> > look at a couple examples in the talk.  If translation to other
> > formats  is an issue, you've got good reason to use a less
> > expressive source format which can be translated more reliably.
>
> --
> 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/47556979-9357-c3d3-b3ed-a3031a195127%40ieee.org.


  parent reply	other threads:[~2021-05-17 12:39 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 [this message]
2021-05-17 21:13                 ` Daniel Staal

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='CAH=xdFt=vJVmJgn9P7hboWa1ExCWVbWrqU5qvZ3Ko8YY2T=YEw@mail.gmail.com' \
    --to=rurquhart-zl5t1cyb3pc@public.gmane.org \
    --cc=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).