Quote:
Originally Posted by Jellby
It is then a matter of the converter supporting the selectors/pseudo-classes/pseudo-elements. Calibre, for instance, performs some CSS "flattening", that removes all complex rules by introducing new classes where needed, this flattened document could then be used as a source for kindlegen or whatever... maybe.
|
Y'know, I got all irritated about this last bit on this thread (not you, Jellby, particularly) on Friday or Saturday, and wrote a big long post...and then decided, "what's the point?," and deleted it.
The short of it is, you can either produce books to
satisfy the readers--by using something like the dreaded SPAN to create pseudo-element effects like :first-line, which will work in EVERY reader, or we can satisfy
our inner geek by putting pseudo-elements in the code--which only WE will see--and let those people who didn't buy the fancier, more up-to-date devices do without.
In the case of indented versus unindented paragraphs, those do, in English, at least, matter.
They certainly matter for scene-breaks, and would have a definite impact on the reader's comprehension of the author's intent. Thus, having a paragraph indent--or not--on all devices actually matters. Not just for those people who can buy a K8 device, but for the millions (millions!) who didn't.
And, Doitsu? I would not, in any sense, rely on the idea that just because you don't get an error message, everything is hunky-dory. Amazon has this cracked idea that the people who use the commercial, more-advanced creation tools, like KG and KP, will actually
read the manual, and see text that
tells them that X isn't supported, and that therefore, they don't need to create an error message for every
possible use of CSS that might be thought up in the depths of our little brains. Unlike the KDP, which is designed for Dummies, their assumption is that we can read the instructions, and
not do stupid stuff.
</mini-rant>
Hitch