Mike Ressler <[EMAIL PROTECTED]> wrote:
> As a side note, I've noticed that diffs are a terrible way of trying to
> see what is different in a LyX doc. The diff itself is impossible to read
> (and this will be especially true as we convert 1.1.6 to 1.2.0 with all
> the inset changes), and applying the doc and opening it in LyX doesn't
> provide any way to easily see the changes (anyone want to code a diff mode
> into LyX :-) Perhaps we should do something "silly" like put all edits in
> blue or underlined or something until the change is mutually agreed on or
> some such. Any recommendations for dealing with this?
>
> P.S. I rather like my LyX diff mode idea --- would this be codable, or is
> it just too messy to contemplate?
>From an experience of my previous life as a lawyer,
I can testify, that there is no other way how to efficiently work with revisions
in _normal document_ (i.e., not source code) than some kind of
"Marking Revisions" mode of the editor (in my case, it was
Word of course, but I am afraid, it is true for any editing task).
It would be quite wonderfull, if the revisions machinery (details may follow,
but see Word95+ or Lotus WordPro) would be included in LyX. It would one
of those steps which would make it different from sole "hiding the LaTeX code"
stuff (which is The Good Thing, nothing against that). However, I am afraid,
that it may get quite complicated. I had not enough courage to propose any
extensions for LyX until the GUII would be completed, but it is close now,
so we can start to dream. :-)
Matej
