Scrivener is all about the forty pages in the chapter, not whether or not the chapter has flawless ready-to-print layout done to it. It’s a tool for writing those chapters from scratch, and managing the massive amount of work that goes into the construction of these chapters, not only the words themselves, but the constellation of supporting data and ancillary material required to make that chapter as accurate and easy to write as possible. It’s about elevating the raw mechanics of writing in an orthogonal fashion to how most word processors work and alleviating the fractured workflows we’ve had to put up with by working in linear document designed applications.
It is not, and probably never will be, a typesetting engine.
I think you do know this one fact, but it is worth reiterating: these endnotes, just because they aren’t placed the way you need them after hitting the compile button, they really are endnotes. That means you can take them into any program and format them however you please later on. They aren’t static text in most cases that you’re stuck with. Like I say I think you get that, because of the follow statement:
That’s exactly the point. Scrivener would cease to be more efficient to use if it was Word and/or InDesign and Scrivener. It would be a monolithic beast that could hardly even lift its own interface. Software cannot reasonably be all things, at least not in this generation of computing. Maybe some day it will be possible to have a supremely elegant drafting tool with a supremely elegant typesetting engine. Maybe it will even be possible for one developer to pull that off, too. Doubtful, but maybe.
Anyway, in this particular world, you’ve got to make choices, and selecting a tool that focusses on a particular aspect of a job can often be more beneficial than trying to pack every conceivable feature into a tool and never straying from it as you transition from one phase of the project to the next.
That all said, Scrivener does have a lot. It’s no slouch when it comes to producing a compile copy. Stack it up against many other dedicated writing programs and you’ll see this to be true, even in its formative state right now, and there is so much more planned and designed in these regards; hundreds already designed. So it can do a lot, and it will be doing a whole lot more as time goes by—but especially for non-fiction, expecting it to do everything Word does just isn’t realistic.
And if that is what you are looking for, something that can replace Word or another desktop publishing program entirely, this probably isn’t the best software for the job. If formatting endnotes in the same software you use to spend a year or two writing the raw material is that important—it’s the wrong tree.
E-books are a trickier matter. This is a brand new field that a lot of us are just now getting in to, and like all brand new fields, the tools for making e-books are still young. Even the venerable old tools that can format a document every other way you can imagine are still lacking in all that could be done for this. We’ve got a lot planned for e-books, but right now for complicated tasks, you still can’t do it all. Organising endnotes by sections in e-books is in fact something on the sooner-than-later list.