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? What happens if you do: context --extra=markdown --help mtx-context | mtx-context | extra: markdown (c:/data/develop/context/sources/mtx-context-markdown.tex) mtx-context | mtx-context | usage: context --extra=markdown [options] list-of-files mtx-context | mtx-context | --sort : sort filenames first mtx-context | --paperoffset=dimension : left-top-offset mtx-context | --duplex : doublesided (singlesided is default) mtx-context | --backspace=dimension : extra left offset mtx-context | --topspace=dimension : extra top offset mtx-context | --bodyfont=specification : additional bodyfont specification mtx-context | --contents : add table of contents
There are limitations in Hans method because you can’t define completely customized styles with it and the basic markdown tags are not enough to produce a document title (should be simple with the multimarkdown extensions).
Or pandoc's extensions.
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). Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------