Thread: Preventing hyphenation in chapter titles?
View Single Post
Old 11-17-2016, 03:52 PM   #13
graycyn
Wizard
graycyn ought to be getting tired of karma fortunes by now.graycyn ought to be getting tired of karma fortunes by now.graycyn ought to be getting tired of karma fortunes by now.graycyn ought to be getting tired of karma fortunes by now.graycyn ought to be getting tired of karma fortunes by now.graycyn ought to be getting tired of karma fortunes by now.graycyn ought to be getting tired of karma fortunes by now.graycyn ought to be getting tired of karma fortunes by now.graycyn ought to be getting tired of karma fortunes by now.graycyn ought to be getting tired of karma fortunes by now.graycyn ought to be getting tired of karma fortunes by now.
 
Posts: 1,591
Karma: 11722446
Join Date: Aug 2010
Location: NE Oregon
Device: Kobo Sage, Pocketbook Era, Kobo Forma, Kindle Oasis 2
Quote:
Originally Posted by Tex2002ans View Post
Is it an ERROR, or is it a WARNING?

What exactly is the Validator saying and what are the settings you are using? If you press on the More Options button in the Validator, you can see more detailed settings (Profile, Vendor Extensions, [...]).

In CSS, it doesn't hurt if the parser runs across properties it doesn't understand. A device that only understands CSS2 and runs across CSS3 "hyphens: none" should ignore it + do absolutely nothing with that information, then just move on.

What you should look out for though is a serious blunder, like a missing/extra ; or {}. ADE absolutely chokes and throws away the entire CSS file if there is any sort of parsing error in the CSS.


  • -webkit-hyphens: none;
    • This applies to any Webkit-based reader (iBooks/Safari, Chrome [I assume Google Play Books is using?], Sigil, Calibre, [...]).
    • Note: Chrome 55 should be finally be introducing the unprefixed hyphens property.
    • Note #2: In Sigil and Calibre you will see zero difference, since their webviewers currently don't implement automatic hyphenation anyway. :P
  • -moz-hyphens: none;
    • This applies to any Mozilla-based renderer (Firefox).
    • Note: Around Firefox 43, Mozilla changed to the unprefixed hyphens property.
  • -ms-hyphens: none;
    • This applies to IE/Edge.
  • -epub-hyphens: none;
  • adobe-hyphenate: none;
    • This is an Adobe-specific recommendation for ADE/RMSDK-based readers (all the older EPUB2 readers, Nook, Bluefire, [...]).
  • hyphens: none;
    • This is the actual CSS3 method of specifying no hyphenation.
I'm not home right now, so I can't check and see what it said, but what I remember is that the W3C validator objected to hyphens: none; because it was CSS 3 and the rest was CSS 2.1? Something like that.

Sent from my Pixel C using Tapatalk
graycyn is offline   Reply With Quote