At some point during the weekend, I suddenly realised that if I published the Innerscape Omnibus to Amazon first, people without Kindles wouldn’t be able to download it at all, for three months. -sigh- I know, I’m fast like that. So this is the revised plan:
I publish the Omnibus as a free PDF first,
Then I publish the epub for free with non Amazon distributors, for 2 weeks?
Then I unpublish both the PDF and the epub so I can offer the Omnibus on Amazon for free.
So here’s where I need some help. I’ve created the PDF, I’ve uploaded it to sync.com, and I have a link for downloading it from sync.com, but I’d kill for some volunteers to test the process. According to sync.com, you don’t need to register or do anything except click on the link and then ‘download’, but the file is over 4 MG, and I’ve grown distrustful in my old age.
So, how about it? Pretty please with sprinkles? 🙂
If you would like to test the process out for me, click the following link and …follow instructions!
I haven’t written any how-to’s on how to create an ebook because I assumed there were countless how-to’s out there already. I was both right and wrong; there are lots of people providing helpful information about text-based ebooks such as novels, but there are not that many devoted to graphics heavy ebooks.
This distinction was brought home to me when one of my blogging friends needed help with a picture book. He was trying to create an ebook with both pictures and carefully formatted text.
It can be done, but the digital technology we have at the moment is limited when it comes to integrating text and graphics.
Before I start on possible solutions, and/or workarounds, I want to explain what those limitations are, and why they cause problems with graphics heavy ebooks.
Things ordinary ebooks can do
Ordinary ebooks are great with text but just barely okay with pictures. That’s because they’re not really ‘books’ at all. They’re more like rolls of toilet paper with words projected onto them. The story literally unrolls in an ebook.
This has significant advantages. For starters, as ereaders don’t care about the size or number of words shown on their screens, the reader can make those words as big, or small, as they please…for the whole ‘book’. I use this feature all the time because my eyesight ain’t what it used to be.
Things ordinary ebooks can’t do
Unfortunately, the very flexibility of ebooks can create problems when it comes to adding pictures to the text. Pictures don’t ‘flow’ the way text does, so getting them to fit the screen requires that they be sized for the screen.
But which screen? There are dozens of different digital devices from smartphones to dedicated ereaders to tablets of various sizes. Making an image to fit one screen almost guarantees that it won’t quite fit another.
Another problem with pictures is that not all digital devices are in colour. Dedicated ereaders, such as ordinary Kindles and Paperwhites, only do grayscale.
To display a picture in colour, the digital device has to be some kind of tablet [like the Kindle Fire] or a mobile phone. So again, which device should you optimise for?
And finally, because of their ability to ‘flow’ the text, ebooks don’t do precise formatting. Unfortunately, graphics heavy books like memoirs, cookbooks, picture books etc, look best when the formatting is controlled and the pictures are in colour.
To work around this fundamental problem with ebook design, Amazon created a number of specialist programs:
Kindle Kid’s Book Creator
Kindle Comic Creator
I took a quick peek at Kindle Kids, and I couldn’t quite work out what it was doing [the manual approach]. I suspect it’s a lot easier if you use the PDF option and simply pour everything into the app in one go.
Of the three, Kindle Create is the one I find most useful. In its current iteration, it is actually two programs in one:
The first allows you to ‘format’ Word .doc and .docx files into text-based ebooks like novels. There is help for creating a Table of Contents as well as Front and Back matter pages, and you can add pictures although the image manipulation is basic to say the least.
The second is the old Textbook Creator app. which turns a PDF document into an ebook.
Kindle Create for text based ebooks
This version of Kindle Create allows you to include all the standard elements of a book as well as pictures, but all you can do with pictures is adjust the size, and sometimes the location. That’s it. You can make the image small, medium, large, or full, but you can only adjust the placement of small or medium images. Large and full images seem to be placed automatically and can’t be changed.
One nice thing is that Kindle Create automatically wraps the text around the image as shown below:
But again, only if the image is small or medium.
This does not constitute ‘total control’ over the way text and images display, but it’s not bad. More importantly, when I did a preview of the page, it seemed to display quite well on tablet, phone and Kindle devices.
Something I was not expecting was that the colour image was automatically changed to grayscale on a Kindle device:
Given that this option works with standard .doc or .docx documents, I was pleasantly surprised by how it put everything ‘together’.
The old Textbook Creator
For the sake of clarity, I’m going to call the second option of Kindle Create by its old name – Textbook Creator.
Textbook Creator doesn’t try to integrate text and pictures at all. It creates an ebook out of a sequence of pictures.
If you’re nodding your head and saying, “Ah, she’s talking about PDFs”, you’d be right.
To quote from one of my own how-to’s:
PDF stands for Portable Document Format. With PDF documents, each page is like a ‘snapshot’ of the original Word page. That’s why it’s called WSIWYG – what-you-see-is-what-you-get.
Basically, everything on the Word page becomes a composite ‘picture’ that cannot change. This is how you make sure that what appears on the screen of the digital device is exactly the same as what you originally created, including the positioning of both graphics and text.
It’s the difference between ‘some control’ and ‘total control’.
“But…PDFs can’t be edited.”
That would normally be true, if you were dealing with a PDF document as a whole. But Textbook Creator cuts the original PDF document into its component pages, and each one those pages can be swapped out, individually.
To make this a bit clearer, let’s say you have imported a 20 page PDF document into Textbook Creator. Then you discover that you made a small error on page 15.
Rather than redoing the whole, 20 page document, you can:
go back to the original,
make a change to page 15,
export page 15 as a new PDF document
swap the new page 15 for the old page 15 inside Textbook Creator, and voila!
Okay, I admit the process is convoluted, but it does make working with PDFs a little less frustrating.
So what is the downside of using Textbook Creator?
The text in the ebook created by Textbook Creator cannot be resized. You can pinch-and-zoom to see details at a larger size, but you cannot specify that the text in the entire ebook be at a certain size.
This means that the original document has to be designed in such a way that it will suit most readers and most ereaders.
In paperbacks, this is kind of standard, and expected, but not so in digital devices. Plus getting the document to fit can be rather tricky.
Getting the size right
As mentioned before, there are a lot of different ereaders out there, and screen sizes are not the same either. Designing a document to fit all of them is a case of picking something ‘average’ and basing the sizing on that.
But what do I mean by ‘sizing’?
The easiest way to explain is to show you. The following is a preview of this post, in Textbook creator:
Can you see how tiny the text below the image is?
All I did was export a standard Word file to PDF and then import that PDF into Textbook Creator. The font size of the Word document is 12.
Now have a look at this preview. Same document but with a font size of 28:
To get the document to display like that, I had to radically change how the Word document was setup. Basicallly, I simulated the Kindle Fire screen in Word so that I could place text and images to their best advantage.
The following screenshots show my page setup in Word 16.
1. Paper size
The dimensions circled in orange create a page size that exactly fits the screen of my Kindle Fire 6.
Again, those margins are designed to make reading the Kindle Fire 6 screen visually ‘comfortable’ without wasting too much space.
Note: there are no settings selected in Layout. You need clean, minimal formatting in the original Word document. This includes not using things we normally take for granted, such as manual ‘spacing’.
For best results, you should always create styles – for the effects you must have – and use only those styles in the formatting.
Because Word is an old program, and Microsoft never throws anything away, it simply buries it under new code. This means that there is a lot of…[expletive deleted]…junk in Word that lurks in the background and can seriously mess with other programs that attempt to read/use Word documents. So keeping the document ‘clean’ is important.
But wait…there’s more. Remember how I said I’d changed the font size to 28? The next screenshot is of the Normal Style I created just for Kindle Fire 6 documents:
I can’t tell you why translating text from Word to a small digital device shrinks the text. All I know is that it does, and we have to manually compensate for it.
The other thing you might want to notice is that the alignment is set to ‘Justified’. Not only does it make the text look more professional, it also saves space on the screen.
To change the Normal Style on your own version of Word, right click on the style [on the Ribbon] and select ‘Modify’ from the drop down list of options [see here for step-by-step details]. That will get you to the Modify Style dialog box shown above.
Once the Modify dialog box is open, change the font size and alignment and then click ‘Save’.
We should now have a document that is optimised for an ebook.
Once the Word document is as perfect as we can make it, save the document as a Word file, and then Export it as a PDF.
Your book is now ready to import into Textbook Creator.
In my next post, I’ll talk about the Textbook Creator software.
When it comes to the cover of your book, KDP offers two tools:
A template builder that specifies cover dimensions for use with a dedicated graphics package such as InDesign,
A free, online Cover Creator app. developed for KDP
Using the Cover Template Builder
The Cover Template Builder generates a template that is exactly the right size for your cover and its spine. These dimensions are based on your chosen trim size and the total number of pages in your book.
To use the template builder, type the following web address into the address bar of your browser:
Before I begin, if you don’t want to self-publish your own paperback, or if you don’t use a PDF file to do it, look away now.
Right, this is the task:
convert your manuscript from a Word 16 [13 and possibly 10] document to a PDF file, in order to print with
Lulu.com, CreateSpace.com or KDP [possible IngramSpark as well]
after converting to PDF, you find that there are fonts in your PDF that are not ’embedded’,
yet after scouring your original Word file, you can find no trace of these non-embedded fonts.
How can you fix something that doesn’t seem to be there?
Before launching into the how-to, let me go back and explain the problem in a little more detail. It all starts with the Word fonts. While Word documents look great on screen and print without problems, sharing them with others can be tricky as they may not have the same fonts on their version of Word.
This is where PDFs come in. They take a picture of your Word file so that it can be shared by just about anyone. However…for PDFs to work properly, all those pesky Word fonts have to be embedded in the PDF. With me so far?
Okay, so how do you know whether the fonts have been embedded in your PDF file or not?
Easy. Download a free copy of Adobe Acrobat Reader. Install it onto your computer and use it to open the PDF file of your manuscript. Once the manuscript is open:
click File, and
select Properties from the menu
With the Properties dialog box open, select the Font tab:
On the Font tab you will find a list of all the fonts used in your manuscript. Next to each one you should see ‘(Embedded Subset)’. I’ve underlined it in green above. If you see a font name without ‘Embedded Subset’ next to it [circled in red above], that means the font is loose and may be replaced with some other font when the reader opens the document [or tries to read your print book].
Now, you could take a chance and shrug the problem off, but printers tend to take a dim view of non-embedded fonts. CreateSpace tags them as errors but allows you to continue anyway. I suspect Lulu will be a bit less forgiving, that’s why I went looking for a solution.
Unfortunately, the solutions offered on the lulu.com website are not particularly useful unless you have an app called Adobe Distiller which is needed to make another app, called Lulu Job Options, work. Guess who doesn’t have Adobe Distiller?
My first brilliant idea was to go back into my Word file and get rid of the unembedded font[s]. Fail. I tried doing an Advanced search for the TimesNewRomanPSMT font, but the search came back with no returns. Given that I never choose TimesNewRoman, I can only think that it’s lurking somewhere in one of Words many defaults.
So then I spent about three, increasingly frustrated hours online, trying to hit on the right combination of search words to find an answer to my problem. I won’t bore you with the failures because the answer, when I finally found it, was right there in Word’s damn defaults. You’ll find it in the File/Options dialog box:
With your Word manuscript document open, click the File Tab.
From the File navigation pane, select ‘Options’:
‘Options’ is where the default options that govern much of the behind-the-scenes stuff lives in Word.
Once you click ‘Options’, the Word Options dialog box opens up. This is the motherlode:
Click Save on the navigation pane as shown [circled in red].
This will open up the Save options, one of which includes the option to ‘Embed fonts in the file’ [circled in red].
Click Embed fonts in the file.
Last but by no means least, uncheck both ‘Embed only the characters used in the document’ and ‘Do not embed common system fonts’. TimesNewRomanPSMT is one of those ‘common system fonts’. -rolls eyes and pulls hair-
Finally, click OK, save your Word file and then convert it to a new PDF file, again.
This time, when you open the new PDF with Acrobat Reader and check its properties, you should see something like this:
And there it is [circled in red], the TimesNewRomanPSMT font…embedded at last!