Michael Gerz wrote:
> Unfortunately, the patch produces some artifacts with dvipost. See file
> cttest.lyx. When exporting to DVI, the text inside the box is not
> aligned with the outer text. If you deactivate change tracking output,
> everything is fine.
But this is not related to your patch, i
On Monday 07 May 2007 17:50:56 Michael Gerz wrote:
> Nevertheless, we should introduce the generalized framework now, not
> after 1.5.0 is out.
>
> > I would like to see how this discussion proceeds, the semantic markup
> > allows some degree of freedom and it is probably one general solution...
José Matos schrieb:
On Saturday 05 May 2007 08:37:28 Jürgen Spitzmüller wrote:
I still think it's too early. With the semanticc markup above, however, we
could put some information (or even a style file) on the wiki, which lets
the user experiment with changes.sty instead of soul.
I
On Saturday 05 May 2007 08:37:28 Jürgen Spitzmüller wrote:
> I still think it's too early. With the semanticc markup above, however, we
> could put some information (or even a style file) on the wiki, which lets
> the user experiment with changes.sty instead of soul.
I mostly agree with Jürgen.
Hello,
the attached patch tries to decouple change tracking output from dvipost.
The overall approach is to define two commands \lyxinserted and
\lyxdeleted that are mapped on either dvipost, soul (in the future), or
"nothing".
Unfortunately, the patch produces some artifacts with dvipost. S
Abdelrazak Younes wrote:
> Michael Gerz wrote:
>>
>> 3. We do nothing, because we don't care about pdflatex output.
>
> I tend to think that pdflatex is the most important output nowadays...
the machine is pdf(e)tex, latex is only a special format and the
LaTeX Companion was created as dvi->ps->
Michael Gerz wrote:
3. We do nothing, because we don't care about pdflatex output.
I tend to think that pdflatex is the most important output nowadays...
Abdel.
Michael Gerz wrote:
> 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
> "change
Michael Gerz wrote:
> 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).
what about soul.sty?
> I also notic
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
10 matches
Mail list logo
