[DNSB]

Originally Posted by JSWolf

Look at the CSS and tell me that it needs to be that complicated when it could be that simple. The way to do eBooks is KISS. StandardEBooks way to do it is Keep it as complicated as possible.

Jon, perhaps you could give an example of just where when reading an ePub, the more complex CSS makes a difference? Perhaps an example such as using margin: auto; which should work with any ePub2 renderer to center images/text but your favourite RMSDK version does not work with it? How RMSDK instead of disregarding an error in a stylesheet dumps that whole stylesheet in the bit bucket? How RMSDK instead of skipping over an unknown CSS entry as mandated by the ePub documentation will sometimes treat it as an error and skip the whole stylesheet?

Are you offended by such items as the body item in the core.css stylesheet where multiple non-standard hyphen items are used? Following from the requirement that unknown items will be disregarded, the old RMSDK used in Kobo ereaders would skip over most of the items other than the non-standard adobe-hyphenate item. Or are you objecting to the Nook specific adobe-text-layout entry in the hgroup entry? Or the disregard for inheritance with the margins being set to 0 in multiple places?

body{
	font-variant-numeric: oldstyle-nums;
	hyphens: auto;
	adobe-hyphenate: auto;
	-webkit-hyphens: auto;
	-moz-hyphens: auto;
	-epub-hyphens: auto;
	text-wrap: pretty;
}

hgroup{
	break-after: avoid;	
	page-break-after: avoid;
	break-inside: avoid;	
	page-break-inside: avoid;
	font-variant: small-caps;
	hyphens: none;
	adobe-text-layout: optimizeSpeed; /* For Nook */
	adobe-hyphenate: none;
	-webkit-hyphens: none;
	-moz-hyphens: none;
	-epub-hyphens: none;
	margin-top: 3em;
	margin-right: 0;
	margin-bottom: 3em;
	margin-left: 0;
	text-align: center;
}

And again, for me, this is why saved search groups were invented and with the conditional run items, it makes it even easier to automatically apply them for my personal use.