forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Johannes Schaefer (JIRA)" <>
Subject [jira] Updated: (FOR-265) visualize diffs between versions of documents
Date Tue, 16 May 2006 09:11:09 GMT
     [ ]

Johannes Schaefer updated FOR-265:

    Attachment: xml-diff-markup.png

There is an extensive body of research about xml-diff, some of them may be found on

The most useful one although dates back to 2002/2004 and was written by N. Walsh (GPL):,

Since documentation is missing it took some time to make it work:
Adapt the configuration file diffmk.xml: remove the xmlns="" namespace declaration from the
<doctype> tag and use the follwing command line:
  $java -jar diffmk.jar --conf diffmk.xml --doctype docbook howto1.xml howto2.xml diff.xml

I'm still exploring how the config file and final markup of changed elements really works,
but since we work with docbook (plugin) I got some forrest output with changes marked up,
see screenshot. (I copied part of the docbook-xsl to the plugin)

The neccessary extra-css is simple:
  .changed {border-left:5px solid red; }
  .added   {border-left:5px solid green;}

Will continue investigating (as time permitts).

> visualize diffs between versions of documents
> ---------------------------------------------
>          Key: FOR-265
>          URL:
>      Project: Forrest
>         Type: New Feature

>   Components: Core operations
>  Environment: all
>     Reporter: Johannes Schaefer
>  Attachments: xml-diff-markup.png
> Forrest may be compared with MS Word that offers the feature to trace changes, add comments
etc. of various authors. 
> How about:
> If there is a file myfile.diff for any myfile.xml:
> Can't forrest render the differences?
> Could look like: Original version in blue font, changes in red, green, ... (or sth like
> User's then could safely change the documentation, get the diff for a former version
(using svn, RCS, SourceSave, whatever) and afterwards review the changes made (maybe with
some external customer).
> There should be an option switch to turn this feature on.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message