>>>> The other way around: Can't we use this to visualize our track >>>> changes in the output document ? >>> >>> Wouldn't you want the review/accept/reject functionality? >>> >> I think the suggestion was to use these macros in our output, not to >> change anything that happens inside LyX. > >Nope. >
As it was my suggestion (as a possible solution of a problem I was trying to fix), I would say 'Yes'. >That would be another totally useless feature. Just like the >"change tracking" feature currently available, but unfortunately >totally useless for Real Work (tm), as it is just a braindead clone >of the functionality provided by MS Word & Co.. > >What is needed for collaborative document authoring in the >Real World (such as companies) is: > >- a built-in subversion client (already available) >- diffing of two versions from the subverion repository with >output _within_ _LyX_ using the "change tracking" display style, >with per-modification accept/reject functionality. > >I've been authoring technical documents for twenty years now >and that this functionality is an absolute "must" für efficient >collaborative document authoring was perfectly obvious to me from >the very first day when I saw what revision control systems are >and how they are used by software developers. So to sum up, you mean: - we don't do real work (or do I miss the joke), - we don't live in the real world (or do I miss the joke), - we are that blind that we don't see what is obvious, - everything we implemented for this feature so far is useless, and - we are braindead. Not really the best way to introduce a feature request. Do you mean that Real People in the Real World doing Real Work all use versioning systems ? >Sincerely, > >Wolfgang Vincent
