Quote:
Originally Posted by Hitch
I think that anyone who's making books for themselves should be able to do whatever they want. It's moot. Once you migrate into making books for others, you have to fall in line with what the reading systems support. {shrug}. That's the boat I'm in, and honestly, I find ePUB to be a fairly smooth, sleek, reading system.
|
I'm not sure we are on the same page here. I am not talking about any kind of different reading format/system. I like epub just fine. Markdown text is what I write (minimally marked plain text files), regardless of target output. When my target is epub, I can generate it with:
Code:
pandoc -o title.epub chap01.md chap02.md ...
Of course, I actually organize my chapters in separate directories, and use a makefile (rakefile) to generate a target, and you'll want to supply your own css file and metadata, but that is beside the point. Markdown is my writing format, pandoc is for generating a target output (be it epub, html, pdf, docx, LaTeX, odt, docbook, etc). I hope that clarifies things a bit Hitch.