View Single Post
Old 11-05-2021, 04:46 PM   #1
DyckBook
Morlock
DyckBook ought to be getting tired of karma fortunes by now.DyckBook ought to be getting tired of karma fortunes by now.DyckBook ought to be getting tired of karma fortunes by now.DyckBook ought to be getting tired of karma fortunes by now.DyckBook ought to be getting tired of karma fortunes by now.DyckBook ought to be getting tired of karma fortunes by now.DyckBook ought to be getting tired of karma fortunes by now.DyckBook ought to be getting tired of karma fortunes by now.DyckBook ought to be getting tired of karma fortunes by now.DyckBook ought to be getting tired of karma fortunes by now.DyckBook ought to be getting tired of karma fortunes by now.
 
DyckBook's Avatar
 
Posts: 34
Karma: 2734796
Join Date: Oct 2021
Device: Kindle Paperwhite
Is @page needed in an ebook?

Many of my ebooks have a page_styles.css with just the following:
Code:
@page {
  margin-bottom: 5pt;
  margin-top: 5pt;
}
A Google search reveals "The @page CSS at-rule is used to modify some CSS properties when printing a document."

So...if I want to read the book on my Kindle not print it do I even need the CSS file?

The reason I ask is that using Modify ePub I can add styles I want, BUT they are added to every CSS file. So I end up with a page_styles.css with all of the styles that I wanted added to the stylesheet.css as well. Safely deleting the page_styles.css file would solve that bloat!

The next question, of course, is, is there a plugin that would allow me to delete a specific file from a set of books?
DyckBook is offline   Reply With Quote