Whenever I write a collaborative document, it undergoes a lot of draft changes. Apart from maintaining the change history in svn, how can I maintain the change history in the tex document itself? I also want it to reflect on the generated pdf.


3 Answers 3


If you want a revision history table showing the following four items, you should look at the vhistory package.

  • Version
  • Date
  • Authors
  • Summary of the changes

If you're wanting the exact revision history from SVN, this might not be the package for you, as this revision history table is created in the LaTeX document. I find this advantageous since I want a more succinct revision history table than every little check-in to git.

Example vhistory code

% Start of the revision history table
  \vhEntry{1.2}{03.02.04}{DP|JPW}{revised after review}

Use the tablegrid option if you want to "display a grid in the table representing the revision history."

Example vhistory output

enter image description here

  • vhistory is exactly what I was looking for! Thank you very much, sir. Commented Oct 24, 2014 at 19:19

I have previously used the svninfo Herbert already mentioned.

But I recently found the vc bundle. It has the advantage/difference of not only tracking the included .tex files but any file in the directory. You will get the global revision, including images or .bib files as well. Apart from svn it supports bzr and git.

On the other hand, it is an external shell-script and not a LaTeX package. Also you will only get the global revision number, not a more fine-grained result depending on current file etc. as svninfo provides.

Supplement: Since it does not use svn properties and special lines in the TeX file, it is completely independent from the svninfo approach and you can even combine both variants.

  • can vc also do the communication (up/download) with a repository? I didn't know it.
    – user2478
    Commented Jan 4, 2011 at 21:13
  • No. It basically just does a svn info and puts the resulting data into a tex command. Commented Jan 4, 2011 at 21:17
  • But then a combination of vc and svn seems to be possible?
    – user2478
    Commented Jan 4, 2011 at 21:37
  • @Herbert; Indeed. I just thought of that myself and added it. Commented Jan 4, 2011 at 21:39

I Use package rcs and put


in the preamble. Then, lines such as:

\RCS $Id:$
\RCS $Source:$

put version information in the formated document.

I notice that there is also a package rcsinfo with a similar purpose, but have not used it.

  • 3
    and also a package svninfo
    – user2478
    Commented Jan 4, 2011 at 18:46
  • 1
    and svn-multi which supports multi-file documents. Commented Mar 24, 2011 at 18:52
  • 2
    and gitinfo... Commented Mar 18, 2013 at 19:29

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .