Quote:
Originally Posted by Hitch
Cyb:
What happens if you remove those spans that are creating the faux smallcaps or drop and incipits? Does it work then?
Hitch's brain is harkening back to a day when using multiple spans in a line, with the ADE engine, caused horrible line-breakage in Nook--I wonder if this could be related? Not directly, but...?
Hitch
|
probably not - I did hack out all the a href stuff and removing that made no difference. From other feedback it does seem that is moon reader app does mess up multi line headers, and more generally is seems to apply its own sizing rules to header tags, ignoring the font size set in the css.
so I'm probably going to not use it after all. I may make up a test file with various styles of h tag lines to test it in more detail, but its come up with too many fails already.
I had another bookread-in-porogress where the chapter number is styled into a black background box, so that number appears as white on black, in a little black square. In moon, instead of a 1 character sized black box, there is a black line all the way across the screen, and on some settings the chapter number therein was invisible. The CSS for that does not apply any colour to the chapter number, so I think is relied on some default interpretation that text written to a black background will be made visible , automatically ?
Code:
<h2 class="h"><span class="black"><span class="txbf">4</span></span></h2>
in that the style for txbf just said to use bold, the class black set a background colour