HI Paul,

following up a message from Richard Webb to Paul Quinn:

PQ> Okay, I want to look at your system... no scripting at this point...

PQ> The daily files consist of some sort of activity logs?  The weeklies
PQ> consist of a compilation for the previous week?

PQ> Ermm... shouldn't that be 0108.txt; 0109.txt; 0110.txt...  :) 
RW> Yep, had to lose the leading 0 in single digit months anyway because
RW> when HOrst's count does its thing it loses it.  I'm
RW> sure you saw that later.

YEp, and it's doing its thing quite nicely.

Oh, yeah, the main program, it does everything to a file
which is named "boatweek.lst" which is the email product
itself.
Within this is current logistical notes, notes on regular
net participants, and of course the info regarding vessels
underway I showed you a sample of, a short humor piece, and
maybe some additional stats.
PQ> Question.  What happens Sunday 5 February, with the 30th & 31st of
PQ> January's logging?  Do they get caught up in "week0212.txt"?

RW> There's a good example of what I've had to wrestle with for
RW> this part of it.  This thing will go out on January 29, as
RW> usual, discussing anything of significance for Sunday the
RW> 29th, Monday the 30th, the 31st, Wednesday the 1st, 2nd, 3rd and
RW> finally the 4th.
RW> The "logging" part of this as I say is already done,
RW> automagically, on the fly.  What isn't and has required some manual
RW> intervention by me was looking through these little
RW> text files to find historic trivia to stuff in there.  For
RW> example, had this been built last week it would have noted
RW> that Thursday the 12th was the 2nd anniversary of the big
RW> quake in Haiti.  A few ham ops really used our network
RW> services to get help to people who needed it.  So that would of
RW> course be in 112.txt, (was 0112.txt) and would have been
RW> automagically posted in last Sunday's history section.
RW> Except, I never got to looking through those last weekend,
RW> hence doing the automation shuffle