Techmology part two: a new (if shaky) hope

I’ve been turning over some pixellated stones on my quest to fix my Kindle ebook’s contents page. The link at the bottom goes to a website by someone called Dark Neon, and I have no idea who they are or what they do. What I do know is that they’ve posted a very handy explanation of what might be going wrong with my ebook’s contents page, and they’ve included a method to fix it. So I’m going to try this tonight, in the hopes that my epublishing career can finally get back on its feet. But you’re probably wondering what the hell I’m talking about. Let me explain:

The problem
My contents page isn’t working. My ebook’s finished in all but the contents page, because I couldn’t get the contents to appear on my Kindle when I was uploading it online through the program MobiPocket. See, a Kindle reader gives you the option to jump back to the contents page to search for chapters in an ebook, by having each chapter set out a bit like a weblink to a particular page. Trouble is, I use Internet Explorer 9, and apparently this and MobiPocket don’t like to work together.

The solution
Uninstall Internet Explorer 9 from your computer and install Internet Explorer 8 instead. At least, this is the theory. I’m going to test it out tonight, and I’ll let you know what happens. I don’t know the code-based intricacies of it, and to be honest by brain can’t grasp them, so I can’t pretend to have much interest in how it works. All that really concerns me, as someone wanting to be an author, is that I can get my book right.

Obviously, there’s a lot more to using MobiPocket to turn your Word file into an Amazon ebook. The table of contents links, how to flag the contents tags up so that they appear in a Kindle document, and other exciting formatting issues have been covered in depth by some very admirable and knowledgeable people. And learning all that stuff is as accessible as starting to type g-o-o-g… into your web browser, really. But I haven’t seen very many guides to this particular contents/web browser problem, so I thought it might be worth making this link known to people if it’ll help. Best of luck if you’re having the same problem, and I’ll let you know how it goes…

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s