Hi,
On 13/11/15 15:26, Peter Uhnák wrote:
For the same reason why Pillar supports export to LaTeX, HTML and
Markdown...why not just one and use pandoc to convert it to
everything? Because control and customizations.
(And that's not even mentioning that some of the powers of Pharo stems
from it's self-centeredness.)
There's open issue for it though
https://github.com/pillar-markup/pillar/issues/8
Well I do use pandoc to convert markup to everything. Mainly because I
thing that is more momentum around scholar markdown[1] and is difficult
to push several light markup languages in this uncharted territory.
Pandoc has support for yaml embedded (arbitrary) data. Of course having
Pillar using markdown + yaml natively and export to LaTeX and HTML will
be the killer feature to stop needing pandoc. Meanwhile I imagine that
at some point I will use AST to hack/extend pandoc with Smalltalk,
bridging these two words and having the advantages of smalltalk and
scholarly markdown for scientific writing... time will tell.
[1]
http://scholmd.org/basic_setup/tools-to-support-your-markdown-authoring.html
Cheers,
Offray
