View Single Post
Old 01-02-2018, 01:45 AM   #9
stumped
Wizard
stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.
 
Posts: 3,305
Karma: 10259306
Join Date: May 2016
Device: kobo forma, Kobo Libra, Huawei media Tab, fire HD10, PW3 HDX8.9,
Quote:
Originally Posted by jackie_w View Post
That sounds like a reasonable guess to me, especially if you accidentally set body {font-size:1; ...} when you intended to type body {font-size:1em; ...}.

It should be easy enough to test.
next time i do a book I will try for the same mistake, deliberately
easy as you say but slow as I cannot test on PC because it looks ok in sigl/ade: I have to get the book onto the tablet ( via calibre & CC ) to see how it looks in moon

as for the earlier modify epub question: i have it coonfigured to remove spans, remove any adobe stuff , update metadata, fix up TOC, update cover.

mainly i use it for auto-fixing the TOC if I have removed any unwanted pages like "also by" or "sneak previews "

starting over would have been the next step ( having checked that original_epub was OK) had the issue not mysteriously gone away again
stumped is offline   Reply With Quote