From: Gour <gour@atmarama.com>
To: ntg-context@ntg.nl
Subject: Re: markdown module vs pandoc
Date: Tue, 19 Feb 2019 14:22:50 +0100 [thread overview]
Message-ID: <q4gvvb$4jrp$1@blaine.gmane.org> (raw)
In-Reply-To: <fab5b8eb-a680-bdbf-a75f-141330ff9271@gmx.es>
On Mon, 18 Feb 2019 17:08:44 +0100
Pablo Rodriguez <oinos@gmx.es> wrote:
Hello Pablo,
> I convert Markdown to XHTML and then I compile the XML sources with
> ConTeXt.
I've tried it and it works nicely. The possibility to have one-source-does-all
is tempting. ;)
Now I wonder if you're still behind the tool and/or whether it is still
actively used by you?
Another question for both you and Aditya in regard to the point made by Mojca
(suggesting to use Asciidoc markup) is whether you find that Pandoc's
(extended) Markdown is semantically rich-enough to cover more complex documents
or in such cases it would be better to use richer markup like Asciidoc or simpy
to directly use ConTeXt?
So far, one thing is clear: ConTeXt is the way to go instead of LaTeX and other
options, but now have to resolve whether to use pandoc's markdown, AsciiDoc or
just ConTeXt...
Sincerely,
Gour
>
> I describe the method at http://www.from-pandoc-to-context.tk/.
>
> Just in case it might help,
>
> Pablo
--
As the ignorant perform their duties with attachment to results,
the learned may similarly act, but without attachment, for the
sake of leading people on the right path.
___________________________________________________________________________________
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-19 13:22 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 [this message]
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
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='q4gvvb$4jrp$1@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).