Quote:
Originally Posted by vr8ce
Why does "Check book" complain about the various CSS "hyphens" directives (hyphens, -epub-hyphens, -webkit-hyphens, etc.)? The directives appear to have been in the epub spec since at least 2.x, and it's part of the CSS3 spec as well. Just about any epub guide that I've seen tells you to use them. These kinds of false positives make it more difficult to go through "real" errors in the check.
(If this has been covered before, I apologize. I've never been able to get MobileRead's "Search" to work — I always get an API error message, on multiple browsers, over several months of trying.)
|
AFAIR, most of those directives are not part of the epub spec. If I feed my stylesheets through the
W3C CSS Validation Service, it comes up with these errors:
Sample output:
Code:
9 -epub-hyphens is an unknown vendor extension
10 -webkit-hyphens is an unknown vendor extension
11 -moz-hyphens is an unknown vendor extension
12 Property adobe-hyphenate doesn't exist
The only one that gets accepted is hyphens : none; if I set the css level to 3.
For an old thread, see
Kobo, Kindle, KOReader and hyphenation for some discussion.