General ⇒ Overview of the changes in your document

[-Robin-]

I was wondering if there is any package that provides the functionality of the
\changes command, as available to the DocStrip tool which processes .dtx files

Code: Select all

\RecordChanges
\begin{document}
Some text
\changes{version}{date}{description}
Some other text
\end{document}

This changes command not only lists the changes at the beginning/end of your document, but is also aware of where it is used ...

I've already found several packages to indicate changes (changebar, changes, ... ) but these all show the changes at the place where the change occurs, and not in a nice overview at the start/end of your document.
Also the version number is a nice feature, allowing to track changes between several revisions.

It would certainly be helpful if someone could point me in the right direction

[drowsy]

I use git.
http://git-scm.com/

[-Robin-]

Yes, we also use a version system, so tracking the changes ourself is not the problem.
It is more for the customers, who only receive a PDF version of the document. It would be a nice to have if we could indicate which parts have been changed since the previous version.

In the meantime, I've been looking into the docstrip.tex to the \changes command, but it looks like Chinese to me

Code: Select all

    \def\change@msg{%
      \edef\@msg{\@spaces\@spaces\@spaces\space
        \expandafter\tospaces\uptospace#1 \qStop\secapsot}
      \let\change@msg\relax}

[localghost]

The changes package might be helpful.


Best regards
Thorsten¹

[-Robin-]

I've looked at the changes package, but this is not what I need.
It has a list of changes options, but there is no version associated to the changes.
So if I have a version 1.0, 1.1, ..., 2.0, there seems to be no way to indicate the changes between version 1.0 and 1.1, the changes between 1.1 and 1.2, ... without removing the old marked changes.
This is all possible with changes command in docstrip for generating package documentation, so I'm surprised it seems not to be available for regular LaTeX files

[-Robin-]

A little bump of this topic, but it contains useful information imho

I found a package which comes very close to what I had in mind, and probably, after some minor adjustments, I will use it for solving my problem(s) described in the starting post: The vhistory package.

Should anyone know any alternatives for this package, feel free to post them so I can take a look at what they offer