Quote:
Originally Posted by Notjohn
Amen!
Aw, Hitch, you really know how to hurt a guy! My workflow is similar: a Word doc becomes an html file, and the html file becomes an epub; later, the same Word doc becomes the print edition via Open Office Writer (which I prefer because I can paginate in it, and because the PDF output is so clean). So, yes, I wind up with two base documents.
But of course I only do a couple books a year, and not always that many.
|
And you are your only client. If you decide to do 100 edits, you inconvenience no one but yourself. And if you realize you have to do those 100 edits after you've created two completely differently-formatted documents, again: nobody to blame but yourself.
Honestly: this is make-work. 'Tis far easier to put a book in INDD, then export the ePUB, tweak the ePUB for *formatting.* Yes, if the client comes back with those selfsame 100 edits, it's the same problem--we have to re-export the ePUB after the edits are made, and retweak the ePUB. But nonetheless--at least the text edits are only made one time, and so you don't have to worry about conforming them.
In commercial bookmaking, there really isn't any good way to ONLY do the book once, given the issues going from print-->eBooks. Not unless you have the privilege of working solely for a BPH. They do the editing rounds until there's simply no life left in it, and you make them all in the print ARCS. There's none of this crackpot "making the books and eBooks and then going back with 50-100 edits post-facto." In trade layout houses, they also do the same thing--all in print until it's flayed.
So, that's that. The only product I know of that accommodates this is, indeed, Jutoh. I've been advised--I don't know this first-hand--that Jutoh also accommodates print, but I just can't warm up to the way Styles (and thus, everything that flows therefrom) work or don't, in that system.
FWIW.
@Harry:
Quote:
|
Would there perhaps be any mileage in making "BookView" a read-only view rather than a window which permitted editing? That would still allow those who wished to use it to copy from to do so, while (perhaps?) simplifying the pain of two-way sync between BookView and CodeView.
|
But, isn't that what PP is now? A read-only view of the code?
Hitch