Quote:
Originally Posted by Tony_A20
Hitch,
I've used the multiple class notation without any problems whatsoever. I design the classes I use to provide incremental styling, and I don't worry about conflicting properties because I try to make sure there are none, but if there were, I would expect the last property applied would replace any previous, conflicting property, and that might be a problem when listing multiple classes.
The thing I didn't know about, was the specification status of an embedded font-family not being inheritable. I understand why such a decision was made, but I don't understand why the special status of the font-family is not better known. I couldn't find anything specific about it in the CSS or HTML spec.
Kindlegen doesn't seem to mind, nor KDP. In fact, I've found the latest release of Kindlegen to be surprisingly forgiving and tolerant, and not at all concerned about many errors. On the other hand, it manages to mention warnings and errors for things (absolute and relative positioning) that the Kindle Publishing Guidelines say are supported—and work. Errors have to be pretty bad nowadays before Kindlegen refuses to produce a .mobi e-book.
I think your doubts about using multiple classes are unfounded. Give it a try.
Tony
|
Tony:
It's highly likely that our experience with mobi format, over the last 5 years, has indeed made us overcautious, but one thing you should be aware of: what works today won't necessarily work tomorrow, at the KDP. And it changes pretty abruptly, sans warning and with EXCEEDINGLY little forgiveness (I mean...are you testing on K4iOS, in a live environment? With incremental inheriteds?).
I don't mean to be so retro that I go "old school" prc, and we don't, but...I know that some of the reading apps, iOS particularly, ARE fragile. That one breaks when you look at it, so...yes, I am
probably overcautious.
Hitch