Thread: Has the ePub check gotten more stringent?
View Single Post
Old 07-01-2024, 04:14 PM   #2
theducks
Well trained by Cats
theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.
 
theducks's Avatar
 
Posts: 31,079
Karma: 60358908
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
Quote:
Originally Posted by phossler View Post
Has the ePub check gotten more stringent? (Win 10, ver 7.13)

I never used to get these errors but now the missing generic message, and there seems to be order constraints in a style sheet



I can fix them by adding "serif' and moving lines around, but I don't think I had to before. This book passed originally with no errors, but now i get these
These have been around since 7.x and maybe before.

The jacket code used to have a couple of empty comments: /**/
In most cases a fresh jacket cures or a saved search

I think some of these were added because of publishers rejections.
I just ignore the 'generic font ones and the order, since my edits are for personal use and my Kobo does not barf.
theducks is offline   Reply With Quote