Believe me, when I tell you that there is no automated typesetting system which can detect stacks and rivers and successfully eliminate them --- moreover, there will not be such a system until such time as fully artificial intelligence comes into existence (and I mean something beyond sophisticated pattern-matching as evidenced by IBM's recent _Jeopardy_ publicity stunt). Every attempt which I've seen which tries to remove stacks gets stuck in endless loops where it can neither remove the stack nor break the paragraph nicely.
I noted specifically in my reply that ePubs re-flow and that the infelicities I referred to would be seen in only a specific viewer implementation, so I don't see why you bring that up.
The bottom line is that for the foreseeable future one has either:
- reflowable text w/ bad paragraph and page breaking
or
- nicely formatted pages which require human attention to create
William
|