View Single Post
Old 12-15-2014, 02:51 PM   #4
Section8
Addict
Section8 ought to be getting tired of karma fortunes by now.Section8 ought to be getting tired of karma fortunes by now.Section8 ought to be getting tired of karma fortunes by now.Section8 ought to be getting tired of karma fortunes by now.Section8 ought to be getting tired of karma fortunes by now.Section8 ought to be getting tired of karma fortunes by now.Section8 ought to be getting tired of karma fortunes by now.Section8 ought to be getting tired of karma fortunes by now.Section8 ought to be getting tired of karma fortunes by now.Section8 ought to be getting tired of karma fortunes by now.Section8 ought to be getting tired of karma fortunes by now.
 
Section8's Avatar
 
Posts: 265
Karma: 2121470
Join Date: Oct 2011
Location: Arlington, TX
Device: Kindle PW4, Moon+ Reader on a cheap Android tablet
This is a .css snipet from test1.epub, which may be part of your problem:
Quote:
p{
text-indent: 5%;
text-align: justify;
font-size: 100%;
margin: 0px;
padding: 0px;
}
The NST has a bug with the shorthand "margin", and (maybe) "padding" css rules. Depending on whether "publisher defaults" is enabled in the Nook (can't remember which way it goes), the Nook doesn't handle these.

Whenever I import an epub into calibre that I'm going to read on the Nook, I always convert all forms of the "margin" shorthand rule to the equivalent margin-top, margin-left, etc in the calibre epub editor as a workaround (the few regexes I've written were for this).

If you're doing a conversion to epub in calibre, somewhere in it's conversion settings there is an option to "expand css" (or something similar) that also does this.
Section8 is offline   Reply With Quote