From: Aditya Mahajan <adityam@umich.edu>
To: Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Processing markdown
Date: Fri, 29 Jul 2011 22:59:04 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.02.1107292241300.18663@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <4E331A39.7040600@wxs.nl>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1364 bytes --]
On Fri, 29 Jul 2011, Hans Hagen wrote:
> On 29-7-2011 8:08, Aditya Mahajan wrote:
>> On Thu, 28 Jul 2011, Wolfgang Schuster wrote:
>>
>>>
>>> Am 28.07.2011 um 00:21 schrieb Aditya Mahajan:
>>>
>>>> @Hans: do you think that it is a good idea to include something like
>>>> this in the m-markdown module so that a user could say
>>>>
>>>> context --usemodule=markdown --mode=process file.markdown
>>>>
>>>> and get a pdf output.
>>>
>>> It’s already there:
>>>
>>> context --extra=markdown file.markdown
>>
>> Does not work. `context --extra=markdown filename` just gives a list of
>> available extras (including markdown), but the file is not processed.
>
> Is there a mtx-context-markdown.tex file on your system?
Yes. But I needed to run mtxrun --generate (my update scripts were not
running this). After that everything works fine.
If I compile a file called 1.md, the output file is called
context-extra.pdf. I think it will be better if the default output is
<basename>.pdf.
> In due time we can extend the parser (given that I know the specs). Btw, the
> more extensions you have, the more one can consider other approached (context
> with export or just xml).
Agreed. Personally, I have now moved from markdown to TeX markup for big
projects (although I have thoroughly tested the xml export).
Aditya
[-- Attachment #2: Type: text/plain, Size: 485 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
___________________________________________________________________________________
next prev parent reply other threads:[~2011-07-30 2:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-23 13:14 [OT] Research into Generative Typesetting John Haltiwanger
2011-07-23 16:37 ` Christian
2011-07-27 10:30 ` John Haltiwanger
2011-07-27 22:21 ` Aditya Mahajan
2011-07-28 8:18 ` Processing markdown (was: Research into Generative Typesetting) Wolfgang Schuster
2011-07-29 18:08 ` Aditya Mahajan
2011-07-29 20:38 ` Processing markdown Hans Hagen
2011-07-30 2:59 ` Aditya Mahajan [this message]
2011-07-30 7:37 ` Wolfgang Schuster
2011-07-30 14:03 ` Hans Hagen
2011-07-30 18:22 ` Aditya Mahajan
2011-07-30 18:15 ` 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=alpine.LNX.2.02.1107292241300.18663@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.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).