ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Andrew Dunning <andrew.dunning@utoronto.ca>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Improving Pandoc Support for ConTeXt
Date: Mon, 19 Oct 2015 21:47:09 -0400	[thread overview]
Message-ID: <D5D6155E-AACF-4612-907A-3ADD10E76AF2@utoronto.ca> (raw)

Dear list,

Pandoc, if you have not heard of it before, is a rather brilliant program for converting text between different markup languages: it allows, in essence, for technology-independent writing. It has been mentioned a few times on this list, with Pablo Rodríguez recently developing a set of templates for typesetting its XHTML output (at https://github.com/ousia/from-pandoc-to-context). One of its aims is to ease the process of producing a high-quality PDF; it has the strongest support for LaTeX at the moment, but it seems to me that ConTeXt would ultimately provide a more reliable and lightweight solution. The basic support is already in place; it only needs to be more thoroughly updated to take advantage of MkIV.

I am working on improving Pandoc's generic ConTeXt template, at <https://github.com/jgm/pandoc-templates/blob/master/default.context>; the initial proposal is at <https://github.com/jgm/pandoc-templates/pull/138>, which aims to show more of ConTeXt’s potential to the user through making variables available that configure its options. I am still new to ConTeXt (having used LaTeX for several years), and could not find a recent starter document. The example at <http://wiki.contextgarden.net/Detailed_Example> is from 2006, and clearly does not exhibit the system’s full potential. I would be grateful to know of any potential areas for improvement.

If you feel even more inclined to develop the Pandoc support for ConTeXt, its writer can be found at <https://github.com/jgm/pandoc/blob/master/src/Text/Pandoc/Writers/ConTeXt.hs>. In my experience, ConTeXt is much easier to use than LaTeX, but it is more difficult to get started with initially due to the lack of resources for new users; it is my hope that full support for it in Pandoc will provide one way of delving into it more deeply.

All best,

Andrew Dunning
PhD Candidate
Centre for Medieval Studies
University of Toronto
http://andrewdunning.ca

___________________________________________________________________________________
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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

             reply	other threads:[~2015-10-20  1:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20  1:47 Andrew Dunning [this message]
2015-10-24 19:11 ` Aditya Mahajan
2015-10-26 11:32   ` Wolfgang Schuster
2015-10-26 16:51     ` Aditya Mahajan

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=D5D6155E-AACF-4612-907A-3ADD10E76AF2@utoronto.ca \
    --to=andrew.dunning@utoronto.ca \
    --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).