- Call to Action: MarkDown in the Reference Library
Re: Call to Action: MarkDown in the Reference Library
toggle quoted messageShow quoted text
Pandoc is indeed what you need. We use it extensively in our toolchain. For most of documents it makes the cut embarrassingly easily and can be scripted. Requires some tweaking at times (like for using ATX style headers).
And also the other way round: making good-looking documents out of simple markdown. You might want to look into Howdyadoc for more clues as to what's possible (includes some custom-made modules written in LUA and python). We use it to make contracts with cross-referenced numbering and stuff, just saying.
Sorry I should have replied earlier. ;-)
Da: "Steve Kilbane" <stephen.kilbane@...>
A: "main@..." <main@...>
Inviato: Mercoledì, 24 agosto 2022 17:51:22
Oggetto: Re: [openchain] Call to Action: MarkDown in the Reference Library
During this discussion on converting to markdown, it was suggested that the Specification was one of the higher-priority targets. Possibly I’m being dense, but where does the master
doc for the spec PDF live? I’m not seeing it in the Specification repo.
A question that came up was “are there tools to do mass/scripted conversion of documents?” As it happens, I was in another meeting today talking about conversion to markdown, and
one of my colleagues pointed me at https://pandoc.org – looks perfect for this job to me.
main@... <main@...> on behalf of Shane Coughlan <scoughlan@...>
Date: Wednesday, 24 August 2022 at 08:17
To: OpenChain Main <main@...>, OpenChain Education <education@...>
Subject: [openchain] Call to Action: MarkDown in the Reference Library
Join email@example.com to automatically receive all group messages.