Quote:
Originally Posted by Sarmat89
That's absurd. You connect the template, assign styles with predefined names, and the converted creates the XML elements basing on those styles, exactly like before. Paragraphs with 'Epigraph' styles are gathered in <epigraph> elements, italics get converted to <em>s... It is not a problem.
|
Well, maybe you could stop instinctively calling everything absurd and listen to what I said.
Currently, styles --> CSS classes.
Styles are applied to paragraphs, and CSS classes are applied to <p> tags.
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?
The two biggest problems with that are a) I am the wizard here, not you, and b) (I'm being serious this time) it seems you hate the idea of ebook producers being allowed to define their own CSS.
(Also a major problem is the need to actually write new ebook converters that can jump through the hoops you want. Do you think code grows on trees?)
(Also a major problem is the fact that you want to force everyone to learn a totally new and radically different approach to designing their books. But you have steadfastly ignored everyone who said so.)
That being the case, this discussion is a non-starter.
You think publisher CSS is bad.
Publishers think publisher CSS is good.
The IDPF agrees with the publishers. I agree with the publishers. Hitch agrees with the publishers. JSWolf agrees with the publishers. Jellby agrees with the publishers. Toxaris agrees with the publishers. In fact, I have never heard of anyone other than you who disagrees with the publishers.
It's kind of like, oh, that your values system has an extreme dissonance with every other values system on the planet.