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