I'm wondering if I have a similar problem as the one had by Mathew Reuther in the following forum thread:
Months of Runaround From KDP Support: Font Embedding Fails...HELP!
He says:
Quote:
So, I'm not 100% positive that this works as I have not fully reassembled the book yet, but KDP apparently errors when you give it a heading declaration with a class that affects the font. Never mind that this is wholly legitimate HTML/CSS...
So, it is absolutely a case of there being a bug in the KDP conversion process. The workaround is moving from this:
<h2 class="fontchange"><a href="link details">Chapter One</a></h2>
to this:
<h2><span class="fontchange"><a href="link details">Chapter One</a></span></h2>
|
That looks altogether similar to what my issue is, guess KDP is choking on valid HTML and CSS once again.
I removed all those useless spans although to be honest the Pages .epub conversion managed to create about 60 separate classes of which I only need about 8.
Guess I'll have to whack a few back in, and test it again.
This thread was from just on a year ago, I thought maybe KDP might have fixed it.