@DipDealer
You would miss my point, when you think I'm someone who resents someone it's joy.
But private things are to distinguish from standard conformity in regards of semantics like they are publically defined by the W3C.
No more, no less.
And semantic markup stands not against suggestions (CSS is a suggestion, which a user can accept or overwrite - by the cascading concept of that language) for the layout.
CSS and the concept of ancestors, neighbors, cascading, ... is very very powerfull.
The most use of classes can be easily avoided without any disadvantage for reaching a specific design goal.
I gave an example in my posting before.
Of course I used "private joy" to provoke.
To emphasize the difference between the intended (by W3C) use of elements and the private ideas of markup.
Some minutes ago I cleaned my first epub completly. It's free of embedded CSS.
And the presentation of it by my Kobo is perfect for my taste!
Even an margin between paragraphs is added automatically by the Kobos internal basic default style sheet. Good luck for me. No need to add any rule at all.
The bad news:
The cleaning needed a lot of time. Sure, now I'm unexperienced in cleaning still.
My next "project": Learning to clean the *.OPF
Little annotation:
Kobo Glo does not recognize a /images/cover.jpg as such.
content.opf: <item href="Images/cover.jpg" id="cover.jpg" media-type="image/jpeg" />
I will habe to place an ugly redundant cover.xhtml
