View Single Post
Old 06-24-2014, 01:04 PM   #7
DomesticExtremis
Addict
DomesticExtremis ought to be getting tired of karma fortunes by now.DomesticExtremis ought to be getting tired of karma fortunes by now.DomesticExtremis ought to be getting tired of karma fortunes by now.DomesticExtremis ought to be getting tired of karma fortunes by now.DomesticExtremis ought to be getting tired of karma fortunes by now.DomesticExtremis ought to be getting tired of karma fortunes by now.DomesticExtremis ought to be getting tired of karma fortunes by now.DomesticExtremis ought to be getting tired of karma fortunes by now.DomesticExtremis ought to be getting tired of karma fortunes by now.DomesticExtremis ought to be getting tired of karma fortunes by now.DomesticExtremis ought to be getting tired of karma fortunes by now.
 
DomesticExtremis's Avatar
 
Posts: 243
Karma: 359054
Join Date: Nov 2012
Device: default
Quote:
Originally Posted by Leonatus View Post
@DomesticExtremis: Thank you for the hint, but there appears:
"Each box has a content area (e.g., text, an image, etc.) and optional surrounding padding, border, and margin areas."
Does this mean - transposed to the use of ebook readers - that one can deliberately decide if he wants, for example, the margins of a text set by controlling the padding, border or margin box commands? Where would I have to assign the @page rule?

That's what I do not understand.
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.

More here.

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.
DomesticExtremis is offline   Reply With Quote