3 ms·

I also wrote a book called the Final Six Days. If you visit his Golden Legacy book page on Amazon you will see my book in the "Others Have Viewed" section. It's

by joeax 10y ago

I also wrote a book called the Final Six Days. If you visit his Golden Legacy book page on Amazon you will see my book in the "Others Have Viewed" section. It's mostly due to me checking on his and other novels. I was planning a Medium article about my (similar) experience. I'm not sure why he'd chose markdown when epub is just structured HTML. If you're a software dev just stick with HTML. Also, to anyone planning a novel: get ready for annoying inconsistencies in display across the various Kindle + iOS + android devices. Fonts not displaying correctly, sizing is off, things not centering, some CSS selectors not being applied at all. It is IE/Netscape circa 1997 all over again.

elliotec 10y ago
What? Markdown is WAY better to write in than HTML, and there are a bajillion converters if worse came to worst
munificent 10y ago
> I'm not sure why he'd chose markdown when epub is just structured HTML. Markdown's a lot simpler/faster to read and write than HTML, and books rarely need the extra features HTML provides. When you do, you can always do inline HTML in Markdown. > Also, to anyone planning a novel: get ready for annoying inconsistencies in display across the various Kindle + iOS + android devices. Fonts not displaying correctly, sizing is off, things not centering, some CSS selectors not being applied at all. Oh yeah. It's even worse if you write a technical book.[1] [1]: http://journal.stuffwithstuff.com/2014/11/03/bringing-my-web-book-to-print-and-ebook/ http://journal.stuffwithstuff.com/2014/11/03/bringing-my-web...
- joeax 10y ago
  I fought getting fixed-width fonts to work for weeks across all these devices. Believe it or not, despite being a sci-fi novel it does have code snippets :)
joeax 10y ago
It's much simpler to just write your novel in Word, generate the HTML, write a small script to scrub out all excess HTML/CSS, then use Calibre to segment into HTML docs by chapter. As far as the HTML for novels is concerned, its very minimal, like a <body> and bunch of <p> tags. I'm not knocking markdown or anything, I just think it's a peculiar choice for writing a novel.

by joeax 10y ago

elliotec 10y ago

What? Markdown is WAY better to write in than HTML, and there are a bajillion converters if worse came to worst

munificent 10y ago

> I'm not sure why he'd chose markdown when epub is just structured HTML. Markdown's a lot simpler/faster to read and write than HTML, and books rarely need the extra features HTML provides. When you do, you can always do inline HTML in Markdown. > Also, to anyone planning a novel: get ready for annoying inconsistencies in display across the various Kindle + iOS + android devices. Fonts not displaying correctly, sizing is off, things not centering, some CSS selectors not being applied at all. Oh yeah. It's even worse if you write a technical book.[1] [1]: http://journal.stuffwithstuff.com/2014/11/03/bringing-my-web-book-to-print-and-ebook/ http://journal.stuffwithstuff.com/2014/11/03/bringing-my-web...

joeax 10y ago
I fought getting fixed-width fonts to work for weeks across all these devices. Believe it or not, despite being a sci-fi novel it does have code snippets :)

joeax 10y ago

It's much simpler to just write your novel in Word, generate the HTML, write a small script to scrub out all excess HTML/CSS, then use Calibre to segment into HTML docs by chapter. As far as the HTML for novels is concerned, its very minimal, like a <body> and bunch of <p> tags. I'm not knocking markdown or anything, I just think it's a peculiar choice for writing a novel.