Table of ContentsIntroduction
Title page including copyright notice and disclaimer
Creating chapters that work
Creating a collection of short stories <<< (NEW SECTION!!)
and a Table of Contents that also works
Alkinea, an .odt to ePub utility
Editing the ePub
Using Kindlegen to generate the .mobi
Cover image, size and where to stick it
Trouble shooting if something goes wrong
IntroductionAfter joining Amazon's KDP I struggled for weeks trying to create my first ebook. It seemed like it should be an easier process than it was turning out to be. Many people, myself included, try and make it more difficult than it really is. Creating your first ebook is easy, if you just follow this tutorial.
The real problem is not that creating an ebook is hard to do, but that it's complicated, involving many steps. To make it more complicated there are other ways to create an ebook, all equally valid, but the steps can be different for each. What works for one method might not work for another. After a lot of frustration, I decided to be more methodical about my testing. I think I now have a reasonable answer. What I present here is the way I'm doing it, and it is both fast and straight forward. In fact it is easy, and if you follow my procedure you will avoid the pitfalls so common in Kindle publishing.
I have an iMac and a Macbook Air, and I make a point of avoiding anything labeled Microsoft, so I use OpenOffice and utilities built for the Mac. I create all of my books and stories using OpenOffice. Keep in mind that ebooks are very simple, so don't use fancy fonts, colors, backgrounds or headers and footers. I stick to Courier New and size 12 for the font.
I have been told that the default fonts used in ePublishing are Arial for sans-serif and Times New Roman for serif, all fonts you use are converted to these two fonts, unless you embed fonts into your document. You can not legally distribute either Microsoft's or Apple's fonts in your document, so don't embed them.
Title PageThe very first page is my title page. I put the copyright notice and disclaimers on the same page as the title in order to reduce the number of pages the reader has to flip through before getting to the meat of the story. Do NOT try and center the title page (or any other page) vertically, it will not work. Put the title at the top of the page, on the very first line, and put no blank lines after the last printable character. I set the title using Heading 1 style so it will show up in the table of contents.
ChaptersBegin all chapters with an Insert->Manual_Break->Page_break and on the very-very first line put the chapter heading (style as Heading 1). I usually center it (but DO NOT USE SPACES OR TABS! Use the center button on the tool bar). Blank Lines are not a sin, unless they're between a page break and a printable character, then they are most heinous. I think space between paragraphs improves readability, and isn't that what we all should be striving for?
I recommend NOT putting a blank line between paragraphs, instead define it in the Style, try these settings: set the default paragraph format to: Before text 0cm, After text 0cm, First line 1.00cm, Above paragraph 0cm, and Below paragraph 0.35cm.
Treat any Forward, Prologue, Introduction, etc, as a separate chapter, just give it the pertinent Heading 1 style header.
Put NO spaces, tabs or blank lines after the last printable character on any chapter or page, else you risk putting blank pages into your ebook. Immediately following the last printable character of the previous chapter is where you insert the page break followed by the header for the next chapter.
Collections of short stories (or breaking a large story into manageable pieces)One of the problems with collections of short stories is that it's so easy to just include the original short story source into the collection. But then you have the problem of maintaining the short story in two different places. Include it again in say a 'Best of' collection and you now have three versions to maintain.
The solution is to define a separate Section for each short story. Start with an Insert->Manual_Break->Page_break, and on the top of the new page do Insert->Section... An Insert_Section dialog box will open. Under the Section tab, under the words New_section type the section name, call it whatever you want but a good choice is to name it the same as the short story. Then click the Link checkbox and click the browse button (...) to locate the short story you wish to include. Under Write_protection click the Protect checkbox (this prevents you from editing the short story in the new collection, you will have to edit it in the original document). Finally click Insert and then close the Insert_Section window.
Whenever you open the story collection for editing OpenOffice will ask if you want to Update all links? if you click Yes the included sections are reloaded into the collection (including any changes you've done to the included file).
You can insert as many short stories (Sections) as desired, and after updating the table of contents (see the following section), it will include all Heading format types that are in the short story. All of the short stories wil be protected in the collection, and can only be edited in their original document.
As well as short story collections, OpenOffice Sections can be used to divide a large document into a few smaller, but more manageable pieces. You could put each chapter in its own OpenOffice .odt file and then insert that into a Section in the encompassing document, or put a few chapters into a small OpenOffice .odt file which would be then inserted into a Section. Either way editing a large document is much easier.
Table of ContentsWhen your book is complete, it's time to create the table of contents. At the end of the front matter insert a page break. That will put a blank page before the first text page. This blank page will be your table of contents. On the table of contents page insert a bookmark with the name toc, nothing else. Do NOT hit Enter or you risk a blank page before the Table of Contents!
Follow these steps for the Table of Contents:
The default font for the ToC heading is rather bland, but you can change it by unchecking the Insert->Indexes_and_tables->Protect against manual changes box. You can then change the font for the ToC just like any other font change. Just be careful you don't change something you shouldn't. And be aware that if you click Update_Index/Table the font for the ToC heading goes back to the default and you'll have to change it again.
If you need to update your table of contents after you change chapter headings, or add or delete chapters, all you have to do is go to your current table of contents, right click on it anywhere and then click on Update_Index/Table and the ToC will reflect the changes, though you'll have to manually change any numbers you inserted into the chapter headings...
Using manually created hyperlinks to bookmarks DOES NOT WORK for a table of contents IN THIS CONTEXT.
AlkineaI use Alkinea to generate the ePub and Kindlegen to convert the ePub into the mobi. Alkinea is fast and it generates the ePub correctly, it does exactly what it's supposed to do. In Alkinea a pointer can be set to Kindlegen, and if you do so Kindlegen will be run automatically.
The advantage of running Kindlegen on your Mac is that it generates the .mobi on your Mac, just the way it gets generated in KDP. You can see any problems before putting your book on the Amazon KDP website.
Alkinea will only work with the OpenOffice created ToC using their Insert->Indexes_and_Tables. The ToC will be wherever you put it in the document.
Well almost only.
If you only put Heading 1 styles at the start of each chapter, but do not use OpenOffice to generate the ToC, Alkinea still has enough information to generate the ToC. In this case Alkinea will create one and put it at the very front of your document.
Editing the ePubIf I need to edit the ePub I use Sigil 0.6.1 (the latest version that will run on my version of OSX 10.6.8 - later versions of OSX can run the latest version of Sigil) and then run Kindlegen manually on the ePub in order to generate the mobi.
I have never needed to edit the ePub, though I thought I had to on occasion. There is always a way to fix any problem at the source, which is where it needs to be fixed. Keeping Kindlegen on your desktop makes life much simpler.
Using KindlegenIf you put Kindlegen into Alkinea and run Alkinea, you should never have to explicitly run Kindlegen, but if you use Sigil to edit the ePub then you will.
It's simplest to have both Kindlegen and your ePub on your desktop. The mobi generated by Kindlegen will also be put there. On your desktop open a terminal window, drag Kindlgen to the terminal window and drop it there, then drag your ePub to the terminal window and drop it there, click on the window to make sure it's active, and hit the enter (return) key and it's done. The only reason I've ever edited the ePub was to see if I could change the title of the ToC, and I could, easily and simply, using Sigil and Kindlegen.
Cover ImageDo not put a cover image in your source file, or give it to Alkinea, since Amazon's KDP will strip it out anyway. If you make your own cover images, make them KDP's recommended size for best quality, 1563px X 2500px (width X height) and pass them to KDP (via Step 4 browse for image button ) when you publish your book. If your cover image is 1563px X 2500px you know exactly what will be on the cover. Other size images will work but they'll be scaled up or down and/or cropped. If you don't have your own cover image, you can use KDP's Cover Creator beta, it works really well and has a reasonable selection of images and cover layouts so you even get one that is quasi-unique. If you have your own photo that you want to use, you can pass it to Cover Creator beta and it'll create the cover using your photo, with KDP's cover layout, fonts, etc it's really kool.
Trouble ShootingWhen trouble shooting, make >1< change at a time and generate the .mobi and check it. The .mobi never has to leave your Mac.
I did no testing with images and other objects embedded in the document, so I can't comment on them.
The mobi generated by Alkinea and Kindlegen works great in both Kindle previewer and Kindle for Mac, as well as on my Kindle 2 and Kindle Voyage.
I can go from an OpenOffice *.odt file to a fully functional *.mobi in about 3 secs (for a 100 page -real 8 x 10 printer pages- novella).
I hope this helps people avoid the frustration and hair-pulling that I had to do...
To sum it all up, or how to make your very own ebook and get rich in 18 easy steps...
Andrew N. Messent, C.C.B.W., any questions
email:Andrew at Parallel