![]() |
#16 |
Bookmaker & Cat Slave
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 11,503
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
|
![]() |
![]() |
![]() |
#17 |
Resident Curmudgeon
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 79,798
Karma: 146391129
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
|
![]() |
![]() |
![]() |
#18 |
Bookmaker & Cat Slave
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 11,503
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
|
![]() |
![]() |
![]() |
#19 |
Curmudgeon
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 629
Karma: 1623086
Join Date: Jan 2012
Device: iPad, iPhone, Nook Simple Touch
|
Want a good approximation of what KF8 readers will do? Open the HTML files in Safari, other WebKit-based browsers, or Chrome. These browsers will let you turn rules off individually, inspect metrics, etc., and with the exception of a handful of bugs specific to the GTK WebKit that Amazon used, a few quirks where Amazon deliberately ignores line height less than 1.2, and Paperwhite's tendency to use an insanely large base font size scaled down (IIRC), which messes with anybody who tries to use explicit point sizes or pixel sizes, you'll usually get a very similar rendering.
|
![]() |
![]() |
![]() |
#20 | |
Bookmaker & Cat Slave
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 11,503
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
Quote:
You sure talk sexy for a squirrel. Hitch |
|
![]() |
![]() |
![]() |
#21 |
Enthusiast
![]() Posts: 43
Karma: 30
Join Date: Feb 2016
Device: none
|
hi, sorry for the delay getting back.
The css is 300 lines (including spaces). What's the best way of me posting that? |
![]() |
![]() |
![]() |
#22 |
eBook Enthusiast
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 85,556
Karma: 93980341
Join Date: Nov 2006
Location: UK
Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6
|
Enclose it in "spoiler" tags.
Spoiler:
|
![]() |
![]() |
![]() |
#23 |
Bookmaker & Cat Slave
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 11,503
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
|
![]() |
![]() |
![]() |
#24 |
Enthusiast
![]() Posts: 43
Karma: 30
Join Date: Feb 2016
Device: none
|
Hi, that's it attached as .txt.
Thanks |
![]() |
![]() |
![]() |
#25 |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 5,735
Karma: 24031401
Join Date: Dec 2010
Device: Kindle PW2
|
There are a couple of syntax errors in your stylesheet:
Code:
h2.toc {
text-align: left; /* semicolon missing */
font-size: 0.5em;
}
Code:
p.paraspacebefore {
/* lines removed */
margin: 1em 0 0 0; /* unit missing */
/* lines removed */
}
Last edited by Doitsu; 03-17-2016 at 06:51 PM. |
![]() |
![]() |
![]() |
#26 |
Curmudgeon
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 629
Karma: 1623086
Join Date: Jan 2012
Device: iPad, iPhone, Nook Simple Touch
|
CSSLint is your friend.
![]() |
![]() |
![]() |
![]() |
#27 |
Resident Curmudgeon
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 79,798
Karma: 146391129
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
delete post
Last edited by JSWolf; 03-18-2016 at 06:11 PM. |
![]() |
![]() |
![]() |
#28 |
Resident Curmudgeon
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 79,798
Karma: 146391129
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Here is the CSS cleaned up somewhat.
Code:
body { orphans: 1; widows: 1; } h1.authorname { text-indent: 0; text-align: center; font-weight: normal; font-size: 1.25em; margin-left: 5%; margin-right: 5%; margin-top: 15%; margin-bottom: 0; } h1.smallcapstitle { text-align: center; font-weight: normal; margin-top: .5em; margin-bottom: 1em; font-size: 2.5em; text-transform: lowercase; letter-spacing: .1em; font-variant: small-caps; } h2.chaptername { text-align: center; margin-top: 1.5em; margin-bottom: 2em; margin-left: 2%; margin-right: 2%; font-size: 1.5em; font-weight: normal; text-transform: lowercase; letter-spacing: .1em; font-variant: small-caps; } h2.about { text-align: center; margin-top: 2em; margin-bottom: 1.5em; margin-left: 2%; margin-right: 2%; font-size: 1em; font-weight: normal; text-transform: lowercase; letter-spacing: .1em; font-variant: small-caps; } h2.toc { font-size: .5em; } h5.copyrighthead { text-indent: 0; font-size: 1em; text-transform: uppercase; margin-top: 2em; margin-bottom: 1em; font-weight: normal; } p.firstpara { text-indent: 0; font-size: 1em; margin: 0; font-weight: normal; } p.para { text-indent: 1.2em; margin: 0; font-weight: normal; } p.paraspacebefore { text-indent: 0; margin: 1em 0 0 0; font-weight: normal; } p.spaced { text-indent: 0; font-size: .85em; margin: 1em 0 1em 0; font-weight: normal; } p.nospace { text-indent: 0; font-size: .85em; margin: 0; font-weight: normal; } p.centred { text-align: center; text-indent: 0; font-weight: normal; } p.connect { font-size: 1em; margin-top: 1em; text-align: center; text-indent: 0; font-weight: normal; } p.acknowl { font-size: 1em; margin-top: 1em; text-indent: 0; font-weight: normal; } p.copyrighttext { text-indent: 0; font-size: .85em; margin-top: .5em; margin-bottom: 0; } p.sectionbreak { text-indent: 0; margin: 1em 0 1em 0; text-align: center; vertical-align: -0.5em; } IMG.titleornament { page-break-before: avoid; text-indent: 0; margin: 0; margin-top: 40%; } /*==Chapter ornament, expands up to 2000px while keeping aspect ratio==*/ div.landscape_large { text-align: center; page-break-inside: avoid; overflow: hidden; clear: both; margin: 1.5em auto; width: 100%; } div.landscape_large img { page-break-inside: avoid; margin-bottom: 5%; width: 100%; } div.centred { text-align: center; } span.centred { text-align: center; } span.i { font-style: italic; } span.b { font-weight: bold; } span.sm { font-variant: small-caps; } span.dropcap { float: left; font-size: 2em; margin-bottom: -0.1em; font-weight: normal; } ul { margin: 1em 0 0 2em; } ul.spaced { margin: 1em 0 1em 2em; list-style-type: none; } ul.toc { margin: 1em 0 1em 0; font-size: 1em; list-style-type: none; } ol { margin: 1em 0 0 2em; } |
![]() |
![]() |
![]() |
#29 | |
Bookmaker & Cat Slave
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 11,503
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
Quote:
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 |
|
![]() |
![]() |
![]() |
#30 |
Enthusiast
![]() Posts: 43
Karma: 30
Join Date: Feb 2016
Device: none
|
Thanks for all. I'll follow the advice.
Just my luck, Amazon have removed the Paperwhite emulation from the Kindle previewer, and it automatically updated. I'll have to dig around for the old one. Trying to buy an old Paperwhite atm. Nobody I know round here has a kindle of any kind. ![]() |
![]() |
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Sigil ignores some CSS-specified fonts | tetrault | Sigil | 12 | 01-29-2016 10:43 AM |
FBReader ignores margin-top | AlanHK | ePub | 24 | 03-25-2015 06:59 AM |
Kindle ignores Title Sort | Ravenswd | Devices | 7 | 02-05-2013 11:04 AM |
Indents and hanging indents in epub poetry | Derek R | ePub | 14 | 02-19-2012 04:43 AM |
fbreader ignores line breaks | red_dragon | OpenInkpot | 3 | 03-20-2009 08:38 AM |