Quote:
Originally Posted by DomesticExtremis
The @page rule applies to paged media - in the case of the e-reader the screen onto which the html document is rendered. you can only set margins with this rule, and they are applied to the 'screen', irrespective of how the html has been flowed or split across pages.
The box model can be applied to any block element, so that you can have different margins/padding/borders for paragraphs, blockquotes and other bits.
You do not have to set an @page, and your e-reader my override/ignore it anyway.
|
This is
very clarifying, and would have helped me a lot in the past (it might help me in the future, hopefully
). I didn't really understand, for example, how it works to make one paragraph extend wider than the other. I only tried some things, waiting for the effects, but it's of course better to understand the context.
You are right: some things work, other do not. Lately, I transferred a book to the reader with the @page rule by Calibre, and the rule was ignored. By hasard, I had to delete this book, worked it up in Sigil (without changing the css), and fetched it to the reader again, and voilą: the margins had become nicer. The world is full of miracles.