Comment Re:I don't understand the version control complain (Score 2) 346
Mod parent up. Seriously. Loudly: TRACK-CHANGES IS NOT VERSION CONTROL.
Say it again: TRACK-CHANGES IS NOT VERSION CONTROL.
"Version" implies, well, a version of a document, a stopping point, a revision of the whole. Tracking a version of a document is a point construct; not at all the same thing as tracking the flow of changes over the course of a period of work. One is a node, the other's an edge. One's a pixel, the other's a vector. Not the same thing.
Both are really useful, but they're different tools for different purposes. As the parent posted, if anyone in a workgroup hits "accept all changes" the tracking is gone. Anyone using track-changes as version control -- expecting never to accept changes, and worse, puttering along with the idea that rolling back through tens of thousands of incremental changes is a remotely practicable rollback function -- is a moron.
On the other hand, true version control is analgous to an audit function. Writers in a workgroup should not be able to defeat version control adopted by that workgroup. Seriously, it should not be easy to lose track of versions or toast the ability to roll back to an earlier version, which in the current state of word processing software (local or in the cloud) means version control has to be external to the document itself. Google Docs' record of explicit saves is pretty close. Wikipedia's history of change commits is dead on. Track-changes is something else entirely.