ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: markdown module vs pandoc
Date: Mon, 18 Feb 2019 17:40:44 +0100	[thread overview]
Message-ID: <CALBOmsZ0nA-ssK0uo6FhgpfNQVezPOykSSJn1_8dW=Q+wLkK4g@mail.gmail.com> (raw)
In-Reply-To: <q44oej$66sg$1@blaine.gmane.org>

On Thu, 14 Feb 2019 at 23:01, Gour wrote:
>
> I'm interested for using markdown markup and typeset such documents via
> ConTeXt, but wonder whether it is recommended to use Markdown module or do
> markdown --> ConTeXt via Pandoc?

If I was you, I would use AsciiDoc, convert it to DocBook and process the XML.
(There is some simple proof-of-concept docbook processing already written.)

Markdown is super ambiguous, with lots of different flavours, and
often resorting to HTML for the lack of more expressive syntax.

> btw, for illustrating
> ConText documents and/or slide-presentation, do you recommend learning
> MetaPost/MetaFun over .eg. TikZ if one wants to focus on single
> (probably my learning plate is already quite full to go into something
> else considering the need to learn ConTeXt itself) package?

I use both.

MetaPost/Fun is really cool when you need a lot of control of what you
want to do, the more calculations you need, the better. There is
relatively little syntax you need to learn to achive nearly anything,
but you mostly need to do stuff from scratch (if you reuse that code,
it gives you a lot of power).

I use TikZ when I need some ready-made stuff with possibly some fancy
shading patterns (or when I would pass the images to LaTeX users). In
those cases you might be able to achive the same in a lot less lines
of code, but you usually constantly need the user manual at hand, and
doing something low level is more tricky. ConTeXt support might be
occasionally broken.

Mojca
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2019-02-18 16:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-14 22:00 Gour
2019-02-15 11:11 ` Aditya Mahajan
2019-02-15 16:49   ` Gour
2019-02-15 17:34     ` Aditya Mahajan
2019-02-17  7:08       ` Gour
2019-02-18 18:37         ` Aditya Mahajan
2019-02-18 16:08 ` Pablo Rodriguez
2019-02-18 17:33   ` Gour
2019-02-19 13:22   ` Gour
2019-02-21 17:50     ` Pablo Rodriguez
2019-02-21 20:59       ` Gour
2019-02-22 19:22         ` Pablo Rodriguez
2019-02-24 11:17           ` Saša Janiška
2019-02-18 16:40 ` Mojca Miklavec [this message]
2019-02-18 17:47   ` Gour
2019-02-18 21:57     ` Alan Braslau

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='CALBOmsZ0nA-ssK0uo6FhgpfNQVezPOykSSJn1_8dW=Q+wLkK4g@mail.gmail.com' \
    --to=mojca.miklavec.lists@gmail.com \
    --cc=ntg-context@ntg.nl \
    /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).