I’ve recently started uploading more technical documents to my Kindle for ease of access. But to compete with paper documents, I have to be able to access the information quickly. This means I rely heavily on the navigation built into the Kindle. I like to be able to jump straight to the Table of Contents, click on the chapter I want, or be able to quickly skip chapters. So what’s wrong with this picture? This comes from a PDF e-book I purchased from CiscoPress and copied to my Kindle. There are 3 major things I have a problem with in this PDF. 1. There are no click-able links in the Table of Contents. 2. The Go To menu is missing an entry for the Table of Contents. 3. There are no tick marks to use the five-way controller for navigation. These are pretty major problems for me because it only allows me to read the document straight through, however I’d much rather be able to skip around through the book. Let’s see if there is a better way to do this…
What we’re going to do is convert the PDF to a PRC file. This will allow us to create the navigation that we want, but it will take a little extra leg work in order to properly apply the finishing touches.
First, Download and Install Mobipocket eBook Creator
Import Your PDF for Conversion
- Locate and Set the Cover Image
- Next we have to edit the .HTML file so that we can find the HTML Anchor names to create our TOC item on the Go To menu.
Here we can see that there is an anchor named “link1” designating the Contents page in the book. We’ll now add this reference as a TOC Guide Item.
- At this point we can either call it quits and build the .PRC file, or we can push forward and create a .NCX file so that we can use the five-way controller for navigation. I agree, let’s move on and do this right.
Araby Greene wrote a great guest article here discussing the NCX file and it’s use in-depth. I suggest you read the article and then come back for a high-level of what you need to add a NCX file to your project. Alright, now that you’re back let’s build our NCX file. You will have to go back to the original .HTML file we edited and search for more anchor names for each of the chapters, and also any other items such as preface, index, appendix, etc. that you may want to add. For my test example I used the Contents page, and Chapter 1 and 2:
Here is a building block example:
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE ncx PUBLIC "-//NISO//DTD ncx 2005-1//EN" "http://www.daisy.org/z3986/2005/ncx-2005-1.dtd"> <ncx xmlns="http://www.daisy.org/z3986/2005/ncx/" version="2005-1" xml:lang="en-US"> <head> <meta name="dtb:uid" content="uid"/> <meta name="dtb:depth" content="1"/> <meta name="dtb:totalPageCount" content="0"/> <meta name="dtb:maxPageNumber" content="0"/> </head> <docTitle><text>Document Title</text></docTitle> <docAuthor><text>Document Author</text></docAuthor> <navMap> <navPoint id="uniqueID" playOrder="1"> <navLabel><text>TextLabel</text></navLabel> <content src="link.html#anchor"/> </navPoint> </navMap> </ncx>
Next, save this file as TOC.ncx and place it in the Publication folder.
Now we have to edit the .OPF project file to add insert a reference to the .NCX file:
The code to paste is:
<item id="ncx" media-type="application/x-dtbncx+xml" href="toc.ncx"></item></manifest><spine toc="ncx"><itemref idref="item1"/></spine>
You are essentially adding an item to the manifest and rewriting the spine.
- We can download and install the Kindle Previewer to open up the .PRC and verify the tick marks show up. Next we can copy the .PRC to the Kindle and enjoy an easily navigable reference document.
We now have click-able links in our Contents page, a shortcut to the Contents page in the Go To menu, and tick marks we can use to skip chapters using the five-way controller. A few caveats though: when importing the PDF into Mobipocket it might not create a link for every item in the table of contents. This could easily be fixed by modifying the .HTML file and adding anchors and links. I feel as long as I get the chapters linked I’m 80% happy. I also noticed that the 13.6mb PDF file I first started with turned into a 6.4mb PRC file.
So if you are as detailed orientated as I am, you can now enjoy your tech docs in geeky bliss.