I read it. It's just not accurate. Wingdings are not really any better. You trade losing the space at a screen turn for having widow/orphan wingdings which are really truly ugly.
Don't take my word for it, go and look at some ebooks. They run at best 50/50 using a non-indented paragraph with extra space above it or some kind of wingding.
Looking at the 2012 top ebooks "Look Inside" at Amazon:
You are once again wrong. Macdonald is right.
One reason you're wrong is that you're making books via what professionals call a text dump and it shows.
Another reason you're wrong is that you're relying on Amazon's Look Inside feature as a measure of how a book will display, which suggests a fundamental gap in your understanding of basic text technology.
Look.
There are two basic ways of creating an ebook, of any format.
One is your method; you're converting files from one format to another using software. That's a text dump.
You're giving up what control an ebook producer has over the display to a piece of software. You're relying on generic app css.
And it shows in your books.
There are two basic methods for creating a quality ebook.
1. Using InDesign with custom scripts, and hand-tweaking the HTML/XML, including the metadata files and the CSS.
2. Creating a very vanilla HTML 4.1 file, and then hand-coding the metadata, XML and CSS files. Then checking the ebook with live users on various platforms.
How Amazon deals with small caps if you upload doc/docx I don't know and as far as I can tell Scrivener doesn't even support them. It may be something you need to add with Sigil or into the raw html.
You're using software like Scrivener and you don't even know how to use it? Yes Scrivener supports small caps; the problem is that there are two sorts of small caps, much like there are two ways of generating italics.
And if you don't know that kind of thing, you're not in a position to pontificate and be snide—especially not to someone like Macdonald, or Old Hack.