[ocaml-infra] markdown in "pure" OCaml

[Sebastien Mondet]

Hi Christophe

maybe that pre- or post- processing is meant to rely on MPP, another
project of Philippe's :) ?
https://github.com/pw374/MPP-language-blender

cheers
Seb





On Thu, Aug 8, 2013 at 1:13 PM, Christophe TROESTLER <
Christophe.Troestler at umons.ac.be> wrote:

> On Thu, 8 Aug 2013 14:14:08 +0200, Amir Chaudhry wrote:
>
>>
>> Christophe, is your example referring to things like the 99 problems page
>> [1, 2], where there are problems posed and clicking a button reveals the
>> solution.  I'm not clear why this would be relevant to the Markdown
>> implementation as html in the markdown file should be fine.
>>  [1] page: http://ocaml.org/tutorials/**99problems.html<http://ocaml.org/tutorials/99problems.html>
>>
>
> The 99 problems page is what I was indeed thinking of.  Of course onecan
> always resort to HTML in case of need but I think that one should take
> opportunity of the "port" of the page to Markdown to do something better.
>  In particular, the text should be closer to the intendedsemantics if
> possible, e.g., say
>
>     @Question
>     ...
>     @Solution
>     ...
>     @Examples
>     ...
>     @end
>
> possibly with a line "@use Questions" at the beginning of the file ifit is
> deemed desirable to announce explicitly the active extensions for a given
> page.  I think such an extension mechanism is desirable¹⁻²⁻³ because it
> uses the principle of least surprise (syntax wise): once you read the
> documentation of the markdown parser, you know what constructs refer to
> outside code.  Otherwise, one may always preprocess Markdown files (adding
> HTML) before passing them to the parser but several incompatible extensions
> may appear (I'll certainly develop one for ocaml.org).
>
> Note that such an extension mechanism may also solve the specification of
> metadata at the beginning of the file (such as "@use template main").
>
> The possibility of adapting the output of standard elements would also be
> desirable.  What if you want to add an anchor to each paragraph or add some
> JavaScript around each code block?
>
> My 0.02€,
> C.
>
>
> ¹ https://pypi.python.org/pypi/**markdown-macros<https://pypi.python.org/pypi/markdown-macros>
> ² http://kirbysayshi.com/2012/**09/17/putting-macros-into-**markdown.html<http://kirbysayshi.com/2012/09/17/putting-macros-into-markdown.html>
> ³ http://pythonhosted.org/**Markdown/extensions/api.html<http://pythonhosted.org/Markdown/extensions/api.html>
>
> ______________________________**_________________
> Infrastructure mailing list
> Infrastructure at lists.ocaml.org
> http://lists.ocaml.org/**listinfo/infrastructure<http://lists.ocaml.org/listinfo/infrastructure>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ocaml.org/pipermail/infrastructure/attachments/20130808/72e3b1ab/attachment.html>