|
Multiple Classes
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
|