Agreed with Tex. The easiest way--which is the gist of your archived posts on Teleread, as opposed to the right way, taken all in--is to use a symbol or fleuron or asterisms. That will work with all systems--I've yet to find one where it didn't--and avoid the issues of the nine-bajillion free "eReading apps" that all recognize whatever they want, and ignore pesky things like the IDPF Standards. (And yeah, Apple, I'm lookin' at you, too!).
{shrug}. Plus to speak to your other point, this way authors don't have to learn to code their books "properly." They can hit enter, center, type 3 asterisks, hit enter and bob's-yer-uncle.
Personally, I prefer top-margins created with CSS, but it's true that in the less-well-known readers and many reading apps, this method can be/might be/could be ignored. (This is why we tell our clients we'll warranty our work on the major devices, but not software eReaders--too many variables, too many obscure pieces, etc. It'll be a cold day in hell before I contort myself or my company and bookmakers to make a book work on Obscure eBook Reader #1,911, you know, just because someone found it on their apps store and it was FREE. I can't tell you how many times we get complaints about a book that looks fantastic on the biggies, but doesn't display EXACTLY the way that the author wanted on some dingbat reading app. And of course, it's never the simpler books that have this issue; it's always the publishers that have had us jump through all sorts of fiddly hoops, that seem to find the least-used eReading apps in existence...)
Even using Scrivener, that should be fairly simple, I'd think?
Hitch
|