Hi, Is there a way to automatically "highlight changes" to a document, such that the resulting PDF has markers showing changed areas? Bars in the margin or some such. Or more generally some other way to easily communicate what has been changed (other than a diff on the source). -- John Devereux
On Tue, Jul 15 2008, John Devereux wrote:
Is there a way to automatically "highlight changes" to a document, such that the resulting PDF has markers showing changed areas? Bars in the margin or some such. Or more generally some other way to easily communicate what has been changed (other than a diff on the source).
I'm sorry, this _is_ a diff on the source: http://archive.contextgarden.net/message/20060806.143457.47021821.en.html But the result can be quite nice. I've also a module, that makes a table to communicate some changes to the reader. It's attached. Typeset it with "texexec --mode=demo t-changes". Cheers, Peter -- http://pmrb.free.fr/contact/
Peter Münster
On Tue, Jul 15 2008, John Devereux wrote:
Is there a way to automatically "highlight changes" to a document, such that the resulting PDF has markers showing changed areas? Bars in the margin or some such. Or more generally some other way to easily communicate what has been changed (other than a diff on the source).
I'm sorry, this _is_ a diff on the source:
http://archive.contextgarden.net/message/20060806.143457.47021821.en.html
But the result can be quite nice.
Thanks, but this (your shell script) did not work well for me - there seem to be too many cases where the diff produces invalid tex code. Did you ever make an extended one?
I've also a module, that makes a table to communicate some changes to the reader. It's attached. Typeset it with "texexec --mode=demo t-changes".
OK, thanks! -- John Devereux
On Fri, Jul 18 2008, John Devereux wrote:
Thanks, but this (your shell script) did not work well for me - there seem to be too many cases where the diff produces invalid tex code. Did you ever make an extended one?
Yes. It's attached. Cheers, Peter -- http://pmrb.free.fr/contact/
Peter Münster
On Fri, Jul 18 2008, John Devereux wrote:
Thanks, but this (your shell script) did not work well for me - there seem to be too many cases where the diff produces invalid tex code. Did you ever make an extended one?
Yes. It's attached. Cheers, Peter
Thanks. I am still finding errors in the result. Some of these are due to lines "commented out" with a leading "%" sign. In others parameter bracket nesting seems messed up. I will play with it some more. -- John Devereux
On Sat, Jul 19 2008, John Devereux wrote:
I am still finding errors in the result. Some of these are due to lines "commented out" with a leading "%" sign. In others parameter bracket nesting seems messed up.
That's why there are these 2 lines: echo Starting editor, so you can manually improve the ConTeXt source. $EDITOR "$OUT.tex" In the normal case, you have to adjust only a few problems by hand. If you comment out normal text, because actually you want to delete it, but you don't really want to lose it forever, then consider using a version control system (subversion for example). Cheers, Peter -- http://pmrb.free.fr/contact/
Peter Münster
On Sat, Jul 19 2008, John Devereux wrote:
I am still finding errors in the result. Some of these are due to lines "commented out" with a leading "%" sign. In others parameter bracket nesting seems messed up.
That's why there are these 2 lines:
echo Starting editor, so you can manually improve the ConTeXt source. $EDITOR "$OUT.tex"
In the normal case, you have to adjust only a few problems by hand.
OK, I will give it a go...
If you comment out normal text, because actually you want to delete it, but you don't really want to lose it forever, then consider using a version control system (subversion for example).
Good point and I am already doing that anyway. The other reason is to quickly enable or disable something. Thanks, -- John Devereux
2008/7/15 John Devereux
Hi,
Is there a way to automatically "highlight changes" to a document, such that the resulting PDF has markers showing changed areas? Bars in the margin or some such. Or more generally some other way to easily communicate what has been changed (other than a diff on the source).
In the same idear, i realy miss something to highlight the « overfull hbox » Olivier. -- [Message tapé sur un clavier Bépo : http://www.clavier-dvorak.org ] http://nemolivier.blogspot.com
On Wed, Jul 16 2008, Olivier Guéry wrote:
In the same idear, i realy miss something to highlight the « overfull hbox »
\version[temporary] \starttext \hsize1pt abcd \stoptext Cheers, Peter -- http://pmrb.free.fr/contact/
On Wed, 16 Jul 2008, Peter Münster wrote:
On Wed, Jul 16 2008, Olivier Guéry wrote:
In the same idear, i realy miss something to highlight the « overfull hbox »
\version[temporary] \starttext \hsize1pt abcd \stoptext
Sometimes, you do not want \version[temporary]. In those cases, I usually use \overfullrule5\points This can also be incorporated in the \version command, \unprotect \def\doversion[#1]% {\chardef\conceptmode\zerocount \overfullrule\zeropoint \processaction % \v!final=> [#1] [ \v!concept=>\chardef\conceptmode\plusone, % simple banner \v!file=>\chardef\conceptmode\plustwo, % full banner \v!temporary=>\chardef\conceptmode\plusthree % full banner plus \overfullrule5\points, % info in the margin draft=>%\chardef\conceptmode\plusfour \overfullrule5\points]} \protect and then one can use \version[draft]. Aditya
Thank's both of you. Exactly what I was looking for. Olivier. -- [Message tapé sur un clavier Bépo : http://www.clavier-dvorak.org ] http://nemolivier.blogspot.com
participants (4)
-
Aditya Mahajan
-
John Devereux
-
Olivier Guéry
-
Peter Münster