3 ms·
I've tried to use Markdown for very simple formatting (to have two consecutive paragraph have a wrapper style, e.g. to have a note style) - and failed. I've tri
by syntern 12y ago
I've tried to use Markdown for very simple formatting (to have two consecutive paragraph have a wrapper style, e.g. to have a note style) - and failed. I've tried various parsers, wrote my code hacks (also called: extensions), regex replacers whatnot, just to conclude, that even if I am able to do that, the live preview will suck.
Fast-forward today: I've started to use Asciidoc with the Atom editor and its Asciidoc live preview. I'm using asciidoctor to generate docbook, and xslt to get it formatted in the way I want. I feel productive to write the content, and I can control every aspect of the output, in the very specific way I see fit.
A simple blog post with a bunch of paragraphs and bold styles may not be worth it, but anything more complex will favor asciidoc.
- ivanr 12y agoOut of curiosity, why not write DocBook directly using a WYSIWYM editor -- for example OxygenXML? Edit: I don't think it's worth using for blog posts and such, but for anything that you plan to publish -- papers and books -- it works very well.
- syntern 12y agoFor me it is easier to version-control and review changes in asciidoc than in docbook.
- ivanr 12y agoDo you review your own changes, or someone else's? Asking because the former is unusual, but the latter works much better with OxygenXML's built-in change tracking. It's fantastic for working with editors (in combination with, say, Subversion).
- syntern 12y agoBoth. Also, I have sometimes a doc edited on google docs, then copied over to local file and formatted in asciidoc. After that we put it back to the google doc in asciidoc markup, and subsequent comparison and merging becomes a way lot simpler.
- thirdtruck 12y agoThank you for introducing me to Asciidoc. I've been using Markdown for my novel drafts, but that may greatly simplify the final conversion process.