Quote:
Originally Posted by Rob Adamson
The latest Pages from Apple is great for generation ePub files for publishing everywhere. It even automagically embeds any non-standard fonts used in your book.
But if you search the web, you will find writers complaining that Pages exports ePubs with a blank line between each paragraph. If you decide to indent the first line of each paragraph, as most books do, then this is a redundant notification of a new paragraph and a big waste of space.
So let’s fix this with Sigil. Remember, Sigil is a low-level editor of ePubs.
Open your Pages generated ePub with Sigil and look around. Then, if you double click on the content.opf file, you see that Pages generated a version 3.0 of the ePub. Also, look at the Fonts section. If you used any non-standard fonts in your manuscript, Pages embeds those fonts automagically into the ePub. Now, anyone viewing the eBook will see the text using those exact same fonts.
This is all great, and Pages seems to be the ultimate ePub generator. But now in your xhtml files (your chapters) look for “white-space re-wrap;” This is the culprit. What you want to do is replace this in every chapter with nothing.
In Sigil you are able to make a global change to all xhtml files. See the following snapshot I used to fix this pesky problem. By doing a find and replace of white-space  re-wrap; with nothing, you can see the blank line between all paragraphs will be removed.
For more tips on self publishing, I wrote this article on Medium:
https://medium.com/datadriveninvesto...g-ae0ab5dfb097
|
With all due respect, you make people go through a lot of extra hoops, in your article. There's no reason on God's green earth why people can't just upload an ePUB t KDP. Making a separate .kpf file using Kindle Create is a lot of extra makework for no reason at all. KC is fine for people who can only barely manage Word and Styles and Headings, but if someone can make an ePUB, it's
silly to use KC.
Hitch