4 ms·
"so you can whip up a "renderer" or converter trivially at any point" And yet almost no one has...
by DidYaWipe 2y ago
"so you can whip up a "renderer" or converter trivially at any point"
And yet almost no one has...
- Y_Y 2y agoTo be fair, one there's a good one there's much less incentive to write something new. In this case the good converter is Pandoc: https://pandoc.org/ https://pandoc.org/
- DidYaWipe 2y agoThanks; but that's a converter, not a viewer. The problem is the lack of READER applications to simply view (not edit or convert) all these Markdown documents.
- Y_Y 2y agoIn my defence, the comment I was replying to mentioned "renderers" and "converters". Furthermore IMHO, any text editor is a Markdown reader. If you want it formatted as is it were "markup" then might I suggest converting to e.g. PDF using Pandoc and then using one of the many capable viewers.
- DidYaWipe 2y agoNoted, re the other comment. But... come on. You might just as well say any text editor is a browser, because you can technically read HTML with it. You can also technically read Word documents with a text reader.
- Y_Y 2y agoI see your point, and maybe it's a matter of preference, but I really do use my text editor for reading Markdown. I wouldn't do the same for a Word doc or HTML, without at least running it through a convertor first.
- geokon 2y agob/c I think people start from the syntax and then think about how to parse it later? A simple grammar probably really limits how you can design your syntax. Here is an example of the problems: https://roopc.net/posts/2014/markdown-cfg/ https://roopc.net/posts/2014/markdown-cfg/