I use Page2RSS for this kind of thing, which I find fairly good. I get quite enough email already.<br><br>Jon<br><br><div class="gmail_quote">On Thu, Jan 14, 2010 at 2:21 AM, David Haslam <span dir="ltr"><<a href="mailto:d.haslam@ukonline.co.uk">d.haslam@ukonline.co.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Another useful service is <a href="http://www.changedetection.com/%0Achangedetection.com" target="_blank">http://www.changedetection.com/<br>
changedetection.com</a><br>
<br>
I monitor a few places like this, including this<br>
<a href="http://www.ibt.org.ru/english/bible/info_bible_en.htm" target="_blank">http://www.ibt.org.ru/english/bible/info_bible_en.htm</a> IBT page .<br>
<br>
David<br>
<div><div></div><div class="h5"><br>
<br>
Gregory Hellings wrote:<br>
><br>
> If the websites have some sort of syndicated feed, like RSS or Atom or<br>
> the like, it would be easy to write a basic script to pull the latest<br>
> info from that. Likewise if there is regular version information in a<br>
> web-accessible version of the file as well as the module's config file<br>
> on the lines of SourceVersion=1.7.6 or SourceDate=1999-10-06 or<br>
> something like that.<br>
><br>
> If that sort of information is not available in a structured way, then<br>
> tracking updates to the upstream material can become far more difficult.<br>
><br>
> --Greg<br>
><br>
><br>
><br>
> On Jan 13, 2010, at 7:37 AM, David Haslam <<a href="mailto:d.haslam@ukonline.co.uk">d.haslam@ukonline.co.uk</a>><br>
> wrote:<br>
><br>
>><br>
>> Do we have any system in place to monitor for changes the websites<br>
>> where our<br>
>> module source texts from from?<br>
>> e.g. When the text itself has been updated.<br>
>><br>
>> Or do we rely on ad hoc knowledge and reporting by interested<br>
>> volunteers?<br>
>><br>
>> David<br>
>> --<br>
>> View this message in context:<br>
>> <a href="http://n4.nabble.com/Watching-websites-where-our-source-texts-come-from-tp1013006p1013006.html" target="_blank">http://n4.nabble.com/Watching-websites-where-our-source-texts-come-from-tp1013006p1013006.html</a><br>
>> Sent from the SWORD Dev mailing list archive at Nabble.com.<br>
>><br>
>> _______________________________________________<br>
>> sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
>> <a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
>> Instructions to unsubscribe/change your settings at above page<br>
><br>
> _______________________________________________<br>
> sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
> <a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
> Instructions to unsubscribe/change your settings at above page<br>
><br>
><br>
<br>
--<br>
</div></div>View this message in context: <a href="http://n4.nabble.com/Watching-websites-where-our-source-texts-come-from-tp1013006p1013096.html" target="_blank">http://n4.nabble.com/Watching-websites-where-our-source-texts-come-from-tp1013006p1013096.html</a><br>
<div><div></div><div class="h5">Sent from the SWORD Dev mailing list archive at Nabble.com.<br>
<br>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br>
</div></div></blockquote></div><br>