From: Gour <gour@atmarama.com>
To: ntg-context@ntg.nl
Subject: Re: markdown module vs pandoc
Date: Mon, 18 Feb 2019 18:47:49 +0100 [thread overview]
Message-ID: <q4er46$73pu$2@blaine.gmane.org> (raw)
In-Reply-To: <CALBOmsZ0nA-ssK0uo6FhgpfNQVezPOykSSJn1_8dW=Q+wLkK4g@mail.gmail.com>
On Mon, 18 Feb 2019 17:40:44 +0100
Mojca Miklavec <mojca.miklavec.lists@gmail.com> wrote:
> 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.)
Uff, even when considering to just use AsciiDoc, I was always trying to stay
away from DocBook. :-)
Do you personally use that?
> Markdown is super ambiguous, with lots of different flavours, and
> often resorting to HTML for the lack of more expressive syntax.
I'm aware of that and that was the reason why in the past I was exploring
reST/AsciiDoc, but then I thƣnk that maybe I can use markdown just for
simpler/shorter content when publishing on web sites via static-site-generator
and for the rest (study notes, slide presentations, alreger texts and/or books)
to simply write directly in ConTeXt markup?
> There is relatively little syntax you need to learn to achive nearly
> anything,
This is something what I like - simplicity is always a virtue.
> 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.
Thank you. It seems that metaPost/Fun is a way to go...
Sincerely,
Gour
--
As a lamp in a windless place does not waver, so the transcendentalist,
whose mind is controlled, remains always steady in his meditation on the
transcendent self.
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2019-02-18 17:47 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
2019-02-18 17:47 ` Gour [this message]
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='q4er46$73pu$2@blaine.gmane.org' \
--to=gour@atmarama.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).