From: Henning Hraban Ramm <hraban@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: other markup to ConTeXt
Date: Sat, 14 Aug 2010 14:47:46 +0200 [thread overview]
Message-ID: <B8086A89-4E34-406F-A72E-7610B33531D0@fiee.net> (raw)
In-Reply-To: <20100814092313.GA30944@aides>
[-- Attachment #1.1: Type: text/plain, Size: 982 bytes --]
Am 2010-08-14 um 11:23 schrieb Philipp Gesang:
> 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).
I was planning on using Python docutils with changing its LaTeX
converter for ConTeXt.
But of course direct LuaTeX parsing of "other markup" would be really
nice.
Markdown, ReST, Creole - I don't really care, as far as there's a
parser in Python, so that I can integrate it in my Django-based Web CMS.
None of their specs is really precise AFAIR, but I guess ConTeXt's
standard markup commands are flexible enough.
Greetlings from Lake Constance!
Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)
[-- Attachment #1.2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2380 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
___________________________________________________________________________________
prev parent reply other threads:[~2010-08-14 12:47 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
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 [this message]
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=B8086A89-4E34-406F-A72E-7610B33531D0@fiee.net \
--to=hraban@fiee.net \
--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).