Quote:
Originally Posted by DNSB
I've seen the same issue in several ebooks where some (expletive deleted) munged the CSS by using absolute units instead of relative units. So a dropcap that was specified in pixels might look good on a Glo (768x1024) but not on a H2O (1080x1430) or Glo HD (1072x1448). The same lack of thought that leads to image sizes specified in pixels so they are look decent on a Touch (600x800), a bit small on a Glo and downright tiny on a H2O or Glo HD.
Sample code for both styles:
Code:
span.dropcap {
float: left;
font-size: 72px;
line-height: 56px;
padding-top: 3px;
padding-right: 6px;
padding-left: 3px;
font-family: "Times New Roman";
}
Code:
span.dropcap2r {
float : left;
font-size : 3.07em;
margin-top : -0.45em;
margin-right : 0.05em;
margin-bottom : -0.5em;
line-height : 1.5em;
}
I have seen some blame placed on Kobo for following the ebook specified style (a shocking thought!) and not scaling pixels to compensate for the screen resolution changes. An issue that can so easily be avoided by using relative measurements which scale. |
The books in question, which I coded myself, use relative measurements (em):
Code:
.dropcap {
font-size : 3.014em;
float : left;
line-height : 1;
margin-top : -0.016em;
margin-right : 0.05em;
margin-bottom : -0.317em;
position: relative
}
Works fine on Akito (reader for Android), Onyx Boox, websites, and the Kobo Glo. Not on the Kobo Glo HD and the Kobo Aura H2O.
The only difference is the software (firmware) version:
Kobo Glo: 3.12.0
Kobo Glo & Kobo Aura H2O: 3.19.5761
Somewhere between those two versions they botched up how dropcaps are handled.
The blame is entirely Kobo's.