Quote:
Originally Posted by mr ploppy
Don't forget that we are just one-man production teams handling everything, so it's very easy to just make the changes to the word processor file. Once you involve other people, whether they are editors, layout artists or whatever, you end up with more than one copy of the word processor file floating around and very little control over what happens to it.
|
I'm neither an author nor do I work in the publishing industry. However I
do work in the software industry, and we've had that problem figured out for decades. When you have more than one person working on source, you
must use some form of version control (and it's not a bad idea to use source control even if you're a one-man show, just because it's always useful to be able to branch off, experiment with changes, and still know that you can get back to the original if necessary). The more robust, the better, so that you can easily go back in time to back out bad changes, track who made what changes, see diffs, etc. It's a solvable problem with an entire industry proving that it works. There's no reason it can't or shouldn't be used for publishing.