Quote:
Originally Posted by DNSB
It doesn't matter how you refer to the glyph. If the font(s) being used to display the glyph do not have the glyph defined, it won't work. Depending on the device you are reading on and the renderer used, some will attempt to locate the glyph in all available fonts while others will use the font(s) defined in the epub.
edit: I ran your epub through epubcheck which had no issues with it. OTOH, validating your stylesheet through the W3C checker came up with multiple errors. Some of them I would disregard but there were several that caused issues on my ereaders.
Code:
1 This profile has a very specific syntax for @charset: @charset followed by exactly one space, followed by the name of the encoding in quotes, followed immediately by a semicolon. @charset "UTF-8";
37 Parse Error [epub|type~="toc"] ol]
41 Parse Error [epub|type~="landmarks"]]
41 Parse Error [epub|type~="page-list"]]
|
Based on your thoughts/findings, I've minimalized the CSS focusing only on the selectors/styles for a single page. But the problem persists, orphan/hanging empty list markers on the following page in the content of the nested lists.
I'm attaching the ePub for your review if you (or anybody else) have time for it.
Thanks.