From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: markdown
Date: Tue, 19 Jul 2011 19:25:11 +0200 [thread overview]
Message-ID: <91CAD91A-6D77-4B8F-A9B2-E554A9194975@googlemail.com> (raw)
In-Reply-To: <4E25BB81.3050607@wxs.nl>
Am 19.07.2011 um 19:14 schrieb Hans Hagen:
> On 19-7-2011 7:08, Khaled Hosny wrote:
>> On Tue, Jul 19, 2011 at 04:05:13PM +0200, Hans Hagen wrote:
>>> Hi Khaled,
>>>
>>> I took a look at the lunamark code, and ran it on some (copied)
>>> sample. As it was much slower than I'd expected from lpeg I messed
>>> around a little and could bring down the runtime on the sample from
>>> 2 sec to 0.1 sec. Anyhow, there is room for improvement so I wonder
>>> If I should take the code, wrap it up a bit, and make a module so
>>> that we can directly process markdown in context. (Of course we then
>>> need to keep an eye on how the original develops, if mkdown develops
>>> at all.)
>>
>> That would be great! That was my intent when I started hacking lunamrk
>> to include a ConTeXt writer, by due to lack of time I never managed to
>> do the ConTeXt module part.
>
> Ok, I'll give it a try and you can do the checking.
Can you then also add a few features:
- Headings use \startstructurelevel
- Paragraphs are enclosed in startparagraph/stopparagraph
- emphasis and bold styles use \definehiglight command
to make it possible to change the layout of markdown documents
where ConTeXt is only used to produce a PDF.
Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2011-07-19 17:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 14:05 markdown Hans Hagen
2011-07-19 14:10 ` markdown John Haltiwanger
2011-07-19 17:08 ` markdown Khaled Hosny
2011-07-19 17:14 ` markdown Hans Hagen
2011-07-19 17:25 ` Wolfgang Schuster [this message]
2011-07-20 12:24 ` markdown Hans Hagen
2011-07-20 13:08 ` markdown John Haltiwanger
2011-07-21 19:31 ` markdown Wolfgang Schuster
2011-07-21 20:58 ` markdown Hans Hagen
2011-07-22 15:42 ` markdown Wolfgang Schuster
2011-07-26 10:16 markdown Hans Hagen
[not found] <mailman.2332.1311677701.4231.ntg-context@ntg.nl>
2011-07-26 12:37 ` markdown Vyatcheslav Yatskovsky
2011-07-26 12:43 ` markdown Hans Hagen
2011-07-26 14:35 ` markdown Paul Menzel
[not found] <mailman.2340.1311697264.4231.ntg-context@ntg.nl>
2011-07-27 0:27 ` markdown Vyatcheslav Yatskovsky
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=91CAD91A-6D77-4B8F-A9B2-E554A9194975@googlemail.com \
--to=schuster.wolfgang@googlemail.com \
--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).