From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: markdown module vs pandoc
Date: Thu, 21 Feb 2019 18:50:41 +0100 [thread overview]
Message-ID: <600a459f-bdf0-65f7-a8f1-134c53190d13@gmx.es> (raw)
In-Reply-To: <q4gvvb$4jrp$1@blaine.gmane.org>
On 2/19/19 2:22 PM, Gour wrote:
> On Mon, 18 Feb 2019 17:08:44 +0100 Pablo Rodriguez wrote:
> [...]
>> 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?
Hi Gour,
sorry for my delayed reply.
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.
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.
My environment is only an example. You may write another one for your
own needs, you don’t have to use mine.
> 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?
I use extended Markdown even for typesetting a ConTeXt introduction in
Spanish (http://www.aprender-context.tk/).
But there are some basic features that I miss from extended Markdown:
- A lightweight syntax for language (such as [Deutsch]{:de}).
- The ability to place the table of contents.
- The ability to place the footnotes/endnotes.
There may be others, but these are the three ones that first came to my
mind .
> 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...
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.
(La)TeX input sources and XML markup are diverse, this is why I think
that pandoc should generate PDF documents from XML sources (and forget
about (La)TeX support).
But this is only my personal opinion. I hope it might help.
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-21 17:50 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 [this message]
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=600a459f-bdf0-65f7-a8f1-134c53190d13@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).