Quote:
Originally Posted by eschwartz
But you'd much rather that an EPUB converter parses the styles to match them up to YOUR arbitrary list, then walk up to the parent node and just automagically turn it into a different element. And what happens to the other styles?
|
1. That's how DOM works. 2. Which other styles? There is no difference between styling <p>s and styling <p>s and <poem>s. You want a heading, you use 2 or 3 styles to make it. What do you need 'extra' styles for?
Quote:
|
I am the wizard here, not you
|
Personal attacks? How quaint.
Quote:
|
you want to force everyone to learn a totally new and radically different approach
|
Assigning styles in a text editor or clicking a toolbar in GUI editor is not radically different.
Quote:
|
You think publisher CSS is bad.
|
No. I think CSS should add to logical layout, not define it.
I still don't know where did you get so many misconceptions about XML. In fact it is like XHTML, only better. They can define the same block/run model. They are interpreted by readers in the same way. The only difference is the powerless HTML with few Ebook-specific extensions and the powerful markup tailored for books.