Quote:
Originally Posted by Psymon
Well, is there really anything "wrong," or "bad," with all that stuff I have in my CSS? If I "should" trim it down, at this point I don't know any more what's necessary and what's not.
|
KISS.
Apply the ligatures to your <p>s or to your specific classes.
But there's no need for it to be on your html, body, fonts, p, classes, [...].
You're just going to cause yourself headaches when you can't figure out CSS Specificity:
https://css-tricks.com/specifics-on-css-specificity/
(What takes priority/overrides what.)
And then you'll be scratching your head as to
why oh why your ligature can't be disabled. (Sound like someone?) :P
Quote:
Originally Posted by JSWolf
ADE (RMSDK) will ignore the CSS 100% if there is one single error.
|
But there isn't an error. It's valid CSS, and how you declare a bunch of this ligature stuff:
Unprefixed forms:
https://developer.mozilla.org/en-US/...ature-settings
Prefixed forms:
https://css-tricks.com/almanac/prope...ture-settings/
Quote:
Originally Posted by JSWolf
And most ePub is read using ADE. Also,I can say that most of that code won't work with the most widely used versions of ADE.
|
Come on, you know better than this!
The prefixed versions work on those specific browser vendors, and are used when the standards are still in flux:
https://developer.mozilla.org/en-US/.../Vendor_Prefix
If the device don't understand it, it don't use it! (It's how you can use CSS3 like rounded borders... where old ADE would just display square edges.)
Just take disabling hyphens:
- adobe-hyphenate: none;
- This was some proprietary ADE/Adobe thing. I personally wouldn't use it.
- -epub-hyphens:none;
- This is a valid way to disable in hyphens in EPUB. (See the specs.)
- -webkit-hyphens:none;
- This would work on iBooks
- -moz-hyphens:none;
- This would work in old Firefox <43.
- I don't believe this is needed any more. Firefox supports the unprefixed version, and they're the ones who are pushing for proper hyphenation.
- hyphens:none;
- Hyphenation is relatively settled in CSS now. This would disable hyphens in anything modern + future.
Like I said. Hideous? Yes.
Would I do it? No (I would leave hyphenation to the device. Disabling would disproportionately hurt smaller devices + those who read with larger font sizes.).