Hello,
although I spent a lot of effort in change tracking, there is still no
way to show changes in pdflatex output :-(
In the past, we discussed whether we should replace dvipost by the two
packages "changes.sty" and "changebar.sty". At that time, some said that
"changes.sty" is too young to be supported.
I played a bit with a mixture of "ulem.sty" and "color.sty" as a
substitute for changes.sty but it didn't work either - lines were not
broken correctly in some cases (maybe ulem or color uses some kind of
mbox mechanism internally). I also noticed that sometimes the color
vanished (definitive a LaTeX bug).
Even worse, I found out that "changebar" cannot handle changes in
sections, subsections, captions, etc (because the changebar information
is moved to the TOC where it breaks things).
In summary, there is no fully satisfying replacement for dvipost and we
have to stick to it for 1.5.X. This said, I am still wondering how we
can support changes in PDF output.
There are basically three options:
1. We define some neutral commands like \lyxinserted{} and
\lyxdeleted{}. If we export to DVI, they map the dvipost commands. If we
export to PDF, they are "ignored". Some power user may overwrite these
commands in the doc preamble to use his/her favourite package.
2. Whether you like it or not: changes.sty does a pretty good job. If
we export to PDF, we could map lyxinserted and lyxdeleted to the
"changes" commands. For DVI output, we keep everything as it is today.
3. We do nothing, because we don't care about pdflatex output.
So, what do you prefer? I can prepare a corresponding patch quite
quickly. In fact, I just have to adapt some patches in my local tree. If
we come to some consensus, we can add this "bug fix" before beta 3.
Michael
