ok, that didn't take long. can't open your .epub file.
it doesn't validate, and i wonder if anyone can open it.
so that's a major problem that you will need to solve...
unzipped it to find out why, and discovered it was made
with calibre. e-book developers hate that program because
it does a rewrite of the underlying .html and .css files,
creating an unholy mess that's very difficult to decipher.
personally, i won't touch a calibre file; life is too short.
aside from the .epub, the .mobi and the .pdf do just fine
in getting the content across, so even though i would likely
have done them slightly differently, what you have is fine.
still, if you really want more feedback, i can give it. but
the original markdown files would be best, concatenated so
they're just one big file, with the text running linearly.
(a book really works best with the whole thing in one file,
because that usually minimizes editorial inconsistencies
while you're writing, and makes it easier to check later.
it also dampens file-clutter considerably, which is good.)
ok, that didn't take long. can't open your .epub file. it doesn't validate, and i wonder if anyone can open it. so that's a major problem that you will need to solve...
Weird. It was generated using InDesign (though I've now learned that opening the .epub in Calibre's ebook-reader will insert a bookmarks file into the zip).
I then used Kindlegen to turn that epub into mobi for sale on Amazon, and Calibre to create the mobi I offer elsewhere. No one has told me they had any trouble opening files and I've viewed them using assorted programs.
(a book really works best with the whole thing in one file, because that usually minimizes editorial inconsistencies while you're writing, and makes it easier to check later. it also dampens file-clutter considerably, which is good.)
I find it easier to break things out into chapter files. Turning the chapters into a Web site even if only hosted locally) makes it easy to navigate through the whole thing. It works for me.
unzipped it to find out why, and discovered it was made with calibre. e-book developers hate that program because it does a rewrite of the underlying .html and .css files, creating an unholy mess that's very difficult to decipher. personally, i won't touch a calibre file; life is too short.
aside from the .epub, the .mobi and the .pdf do just fine in getting the content across, so even though i would likely have done them slightly differently, what you have is fine.
still, if you really want more feedback, i can give it. but the original markdown files would be best, concatenated so they're just one big file, with the text running linearly.
(a book really works best with the whole thing in one file, because that usually minimizes editorial inconsistencies while you're writing, and makes it easier to check later. it also dampens file-clutter considerably, which is good.)
-bowerbird