On Mon, 17 Dec 2012, Allin Cottrell wrote:

I'd be very glad to receive suggestions on the best way of keeping

the translations reasonably up to date.

After thinking about it, here's one proposal. All the specific
timings below are notional and subject to debate.

1) I designate a subset of the gretl web pages in CVS as "core"
pages and publish this list.

2) I set up a cron (automated batch) job to scan the translations of
the core pages each week. If a translation is found to be more than
three months behind the English version then an automatic email is
sent to its author, saying that if the translation is not updated
within a week it will be replaced by the English version.

3) The cron job detects if a page was flagged, as decribed above,
the previous week and has not been updated. If so, it uploads the
English page to sourceforge in place of the translation. (For
example, if the language in question is "xx", it overwrites the
translation, gretl_foo_xx.html, with the English version,
gretl_foo.html.) It could also send out a second email saying that
this has happened.

4) The cron job keeps a list of any pages that have been replaced in
this way, and if an updated version lands in CVS the translated page
is restored on sourceforge.

Allin
_______________________________________________
Gretl-devel mailing list
Gretl-devel@lists.wfu.edu
http://lists.wfu.edu/mailman/listinfo/gretl-devel