Quote:
Originally Posted by Hitch
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.
|
Indented paragraphs do of course matter if they indicate scene breaks etc. However, in my experience they're not uniformly used. For example, in some books the first paragraph of a chapter is indented while in others it isn't. The same goes for paragraphs interrupted by tables, images, poems etc.
It's these cases that
Dylan Tomorrow's use of the
:not selector primarily addressed and which otherwise would have to be handled by manual style overrides. And, as I mentioned in my earlier post, the
:not pseudo selector is not on the black list of prohibited pseudo selectors in the Kindle Publishing Guidelines.
Quote:
Originally Posted by Hitch
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.
|
IMHO, it's indeed a "cracked idea" to assume that users do read the manual, and, based on my personal experience, most software developers target their software at the most
stupid uninformed user and do their utmost to ensure that input and output files comply with whatever standard they decided to support, because it'll make it easier to bugfix and support their software in the long run.
You're of course right in that the absence of an error message doesn't necessarily mean that a feature is supported, because a sloppy or overworked software developer might have missed implementing an error check for it.