Ugh, so close... I've been working on translating a scanned PDF [1] back to Markdown, and I've stumbled on some issues: * we're kinda targeting Github Flavore

Ugh, so close... I've been working on translating a scanned PDF [1] back to Markdown, and I've stumbled on some issues: * we're kinda targeting Github Flavored Markdown, but there's also an online version which uses Docsify, and some incompatibilities have tripped me up: hard line breaks, specifically. * I've tried Mou and MacDown to edit, and the preview pane drifts out of sync, and sticks there. Both require awkward tricks to reload the files if you edit them elsewhere. * diagrams and math formulae are, well, I'm kicking the can down the road on those. * footnotes with text aren't exactly standard yet. Glancing at Dillinger and StackEdit, mentioned in the article, I see other issues: * multiple lines aren't automatically paragraphs * StackEdit sorta supports diagrams and math expressions, but, not in a way they'll render on the target. Having vented about all that, to come back to the article: this is still far preferable to Word. These obstacles don't feel insurmountable, and I was easily able to whip up tooling to go back and forth from one file for the book to a file per chapter, and it's mostly easy to track changes with git and Github. [1] PAIP, previously discussed here: https://news.ycombinator.com/item?id=16469167 https://news.ycombinator.com/item?id=16469167