From: Gour <gour@atmarama.com>
To: ntg-context@ntg.nl
Subject: Re: markdown module vs pandoc
Date: Thu, 21 Feb 2019 21:59:00 +0100 [thread overview]
Message-ID: <q4n3el$2iot$1@blaine.gmane.org> (raw)
In-Reply-To: <600a459f-bdf0-65f7-a8f1-134c53190d13@gmx.es>
On Thu, 21 Feb 2019 18:50:41 +0100
Pablo Rodriguez <oinos@gmx.es> wrote:
> sorry for my delayed reply.
No problem - there is no rush here. ;)
> I’m still behind the environment itself, although I realized that
> these may not be relevant to everybody. I store the new commits in a
> private repository.
Aha...I believe I might be interested. :-)
> I use the XML handling (generating the XHTML with pandoc) in ConTeXt
> for almost all the documents I compile with ConTeXt. I think this is
> the way to go.
I admit it sounds/looks very good. Morever, it could allow me to e.g. use
org-mode for my original markup which I use anyway with Emacs and then do
org-mode --> XHTML.
> My environment is only an example. You may write another one for your
> own needs, you don’t have to use mine.
Heh, for that I must learn some things first. :-)
> There are other options, but LaTeX is a real problem for the
> development of pandoc, because many times users expect pandoc as a
> layer that spares them the actual dealing with LaTeX.
ConTeXt is certainly more appealing..
> But this is only my personal opinion. I hope it might help.
Thanks you very much!
Sincerely,
Gour
--
It is far better to discharge one's prescribed duties, even though
faultily, than another's duties perfectly. Destruction in the course
of performing one's own duty is better than engaging in another's
duties, for to follow another's path is dangerous.
___________________________________________________________________________________
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-21 20:59 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 [this message]
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='q4n3el$2iot$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).