I totally admire every one of you who self-publish, create your own covers, and somehow have figured out how to get your books on Kindle and the Nook and all the other gadgets. I totally freaking admire you.
Never more so than when I read an article by David Gewirtz on ZDNet called, Six Tips for Getting Apple’s iBooks to Accept Your EPub File.
He began to lose me in the third paragraph when he wrote “… I attempted to sign in to iTunes Connect using my iPhone developer account…” Huh?
My eyes glazed over at: “The container.xml file contains a reference to the content.opf file, which, in turn, references the toc.ncx file. Here’s the thing: the content.opf and toc.ncx files are key to making all this work.”
Now I know a bunch of you are super smart folk who can probably speak the language that includes things like “META_INF” and “OEBPS” and:
I’d originally used UltraEdit on the PC, and when I moved the files to the Mac, I used TextWrangler. TextWrangler allowed UTF-8 encoding, but listed files as “(no BOM)” meaning the encoding isn’t prefaced by a multi-byte bill-of-materials. This didn’t seem to be a problem.So, somebody zip over, read this article, and tell me what in the heck Gewirtz is saying. If you do understand it, is the process as hard as it sounds? Or does he make it crystal clear to those of you who speak computer? Then come back and tell me so my head will quit spinning around.