Not sure how difficult it would be for example to generate a mail with all pages that have changed or have been added at the end of the doc
All that needs to be done, would be creating a changelog from the cvs log of the different language folders and then replace the filenames ...
For the most end users it would make no much sense to have a simple weekly CVS changelog mail or website - nobody is interested in knowing a typo fix or fix in a single line of text or an example.
But status idea is good, so how to realize it?
New or deleted "pages" (methods, intro sections) can be detected by comparing an old chapters.ent against a new one. So after a weekly build we could save the old one and compare it to the file after the build a week later.
Significant changes in texts of existing pages could be detected by counting the changed lines between to versions, for example more then 3 coherent lines.
Also we could introduce special tags for the CVS commit message to mark a relevant change.
--
Alexander Merz
http://www.alexander-merz.com