From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: markdown module vs pandoc
Date: Fri, 22 Feb 2019 20:22:32 +0100 [thread overview]
Message-ID: <9c354467-63d0-a715-ea3a-4f0d0fe02ff0@gmx.es> (raw)
In-Reply-To: <q4n3el$2iot$1@blaine.gmane.org>
On 2/21/19 9:59 PM, Gour wrote:
> On Thu, 21 Feb 2019 18:50:41 +0100 Pablo Rodriguez wrote:
>
>> 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. :-)
Hi Gour,
the code in my private repository is unnecessarily complex for too
narrow cases.
I think that the most valuable feature of environment itself (the file
'pandoc-xhtml.tex') is the practical introduction to “Dealing with XML
in ConTeXt” (http://pragma-ade.com/general/manuals/xml-mkiv.pdf).
>> 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.
ConTeXt only requires XML source as input to typeset it.
>> 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. :-)
The published code is fine for what you want. The latest version would
be misleading. It is crappy in many aspects (even for myself).
>> 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..
ConTeXt deals with XML natively.
Cheers,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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-22 19: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
2019-02-21 17:50 ` Pablo Rodriguez
2019-02-21 20:59 ` Gour
2019-02-22 19:22 ` Pablo Rodriguez [this message]
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=9c354467-63d0-a715-ea3a-4f0d0fe02ff0@gmx.es \
--to=oinos@gmx.es \
--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).