[arspr]

Originally Posted by GeoffR

The difference with the kepubs results could be that I am adding margin/padding to the device's built-in stylesheet, rather than to the book's stylesheet, and testing with synced kepubs.

Unless you are speaking about another thing, I still cannot replicate your behaviour. I've redone the tests using kobo-book.css instead of the book internal css tables and everything continues as I posted before.

Look at the first attached picture. That book (it's Jellby's updated test book from here) has body {margin: 0; padding: 0} but I've set body {margin: 1em} through kobo-book.css. And you can see how the trimming issue is gone.

(Although, as I said, it reappears if I set the device margin setting at 0. In that picture it is actually set at 1, I mean, at the next possible minimum value in the GUI slider).

Originally Posted by GeoffR

The font cut-off doesn't happen at all in the epub reader, even with a zero margin.

Look at the second picture. As I said, within epubs you can get trimmed characters because RMSDK does support a true 0 value in the margin. So yes, part of your characters are in fact outside of the screen... and therefore they are "trimmed".



OTOH and somehow offtopic...

I don't like how kepub-book.css is working...

I mean the exact kepub-book.css code I've used is:

body {
margin: 1em;
}

But the book has an explicitly style set inside:

body {
  margin: 0;
  padding: 0;
}

So the kepub-ebook.css one shouldn't have been applied!!! I should have need !important in the kepub-book.css code. Why is an external CSS setting overriding an internal CSS one?