Quote:
Originally Posted by Doitsu
There are a couple of syntax errors in your stylesheet:
<snip CSS>
Also KindleGen will ignore all -epub and adobe-hyphenate entries.
|
Yes, that. ^ Fix the mistakes, remove the -ePUB and adobe entries, just so you have an easier time troubleshooting.
Also, I too would suggest CSSLint. You have some...not coding ERRORS,
per se, but things you oughtn't to do. For example, you appear to be using H1 as a STYLING mechanism, rather than a hierarchal mechanism. This is not good. I will forebore my ubiquitous lecture on the topic of
"pay attention to what things ARE, not what they look like," but take that sentence to heart. (You hear it so often around here that even notjohn is beginning to repeat it at the KDP.)
Now...I do not see--I admit it--why on earth the PPW is giving you fits. Of course, we're only viewing the CSS. It's a tiny bit limiting. :-)
I have two comments, which may or may not be relevant:
I notice that you don't have p itself defined. I know that this sounds ridiculous--and I have
no proof--but lately, it seems like everyone who comes to me with some weird problem has NOT defined the basic p class. Worst case, it won't hurt.
For the purposes of troubleshooting, I'd do two things in this regard--I'd define the fundamental p class, as the first-line indent, no margin element you want it to be, AND, I'd move the p.para above (earlier) in the CSS sheet than p.firstpara. So, p first, then p.para, then p.firstpara.
(BTW: p.para is redundant. You can just define P as this class, and omit p.para altogether, for what that's worth.)
Are you testing on a real Paperwhite or the emulator?
I would do each of those things,
one at a time, to see if it makes ANY difference. Also, if you are not testing on a real paperwhite, send it to someone who has it (the post-Step 7 mobi, not your post-Kindlegen mobi), and see if they see the same thing. The Previewer IS very reliable, I find; it never hurts to be sure.
So: clean up the CSS mistakes, step 1. Test that. Add the basic p class, step 2. Test that. Move the classes around to the proper order of inheritance, step 3, test that.
If none of that works--you have a real conundrum. P.S.: if you are not testing on real devices, how do you know if your font call to Georgia is working? Given that the Fire emulator
only displays Georgia, generally?
Hitch