ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Philipp Gesang <pgesang@ix.urz.uni-heidelberg.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: other markup to ConTeXt
Date: Sat, 14 Aug 2010 11:23:13 +0200	[thread overview]
Message-ID: <20100814092313.GA30944@aides> (raw)
In-Reply-To: <20100814071917.636bc5fe@atmarama.noip.me>


[-- Attachment #1.1: Type: text/plain, Size: 1480 bytes --]

On 2010-08-14 <07:19:17>, Gour D. wrote:
> Finally, for the high-quality output, we plan to convert to ConTeXt
> (via pandoc since there is no ConTeXt writer for sphinx/docutils) for
> high-quality PDF output (if rst2pdf won't be satisfying or if we would
> like to provide paper putput.

Hi Gour, Hraban, John, and the list,

did you consider directly processing reST or similar markdown with
context using lua? Certainly it has advantages to have a converter output
context (backslash style) code and being able to finalize it. But
implementing some .rst processing directly in context shouldn't be that
hard (and with luatex you could handle the html output as well). 

Has somebody already made some steps in that way?  (I'm thinking about
doing so for quite some time now but then, it's not that pressing
either.)

Philipp


> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________


-- 
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments

[-- Attachment #1.2: Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 486 bytes --]

___________________________________________________________________________________
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:[~2010-08-14  9:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-13 11:03 simplefonts or Typecripts Gour D.
2010-08-13 15:58 ` Hans Hagen
2010-08-13 16:50   ` Gour D.
2010-08-13 19:11   ` Gour D.
2010-08-13 20:35     ` other markup to ConTeXt (was: simplefonts or Typecripts) Henning Hraban Ramm
2010-08-13 22:56       ` John Haltiwanger
2010-08-14  5:19       ` other markup to ConTeXt Gour D.
2010-08-14  9:23         ` Philipp Gesang [this message]
2010-08-14  9:31           ` John Haltiwanger
2010-08-14  9:50             ` Khaled Hosny
2010-08-14  9:52           ` Hans Hagen
2010-08-14 10:23             ` Philipp Gesang
2010-08-14 12:47           ` Henning Hraban Ramm

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=20100814092313.GA30944@aides \
    --to=pgesang@ix.urz.uni-heidelberg.de \
    --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).