Oh well, I do use CVS! Note that these tools find difference of structure of the template. (My first post was just a little ambiguous for this point. Thanks for pointing this)

What this tool (possibly) solves is the situation below:

Programmers make a simple template

First you'd make a bare bone template like this:

<TABLE>
[% FOREACH p = product %]
<TR><TD>name: [% p.name %]</TD></TR>
[% END %]
</TABLE>
[download]

okay, this HTML is very simple.

Designers migrate this template into production ready style

Their HTML is kind of hell, with various TABLE tags or something. (Oh well, stop argueing about style-sheet vs TABLE tag here). They possibly have difficulty in migrating the barebone template into production ready design. They'd make typos in template variable name, or forget to paste some code chunks in the template.

Then ttdiff and htdiff will find the structual differences between the two template. It can work more nicely with CVS, off course!

--
Tatsuhiko Miyagawa
miyagawa@cpan.org