RE: Recurrence question regarding Februaries

> -----Original Message-----
> From: [email protected] 
> Try sending an DTSTART and RRULEs your are talking about.

OK.  This was a hypothetical example, but I'll give it a shot:

  DTSTART;TZID=US-Eastern:20040201T000000
  RRULE:FREQ=DAILY;INTERVAL=2;BYMONTH=2

(Hopefully I've just encoded a start time of February 1, 2004 at the leading
edge of the first second in the day, and hopefully I've also just expressed
a recurrence rule that says "every other day in February".)

My question is, given those RFC 2445 snippets, and given an arbitrary date
that is NOT in the recurrence set defined by those snippets, what must I do
to such an out-of-range date to bring it into conformance?  So, given, e.g.,
April 30, 2005, what would I have to "do" to it to get it to meet the
conditions of the recurrence rule defined above?  That is, if I add time to
this date such that it "enters" February, 2006, when do I stop adding time
to it?  When it has reached February 1?  When it has reached February 2?

(If I hear you correctly, you're implicitly saying that a recurrence rule is
meaningless without a start date, because, in part, of the very question
that I'm asking (i.e. "what does 'every other day' mean when there's nothing
to 'anchor' it to?").  So saying "every other day in February" is
meaningless without first specifying, e.g., "where the first day of this set
is February 1, 2004".  Is that correct?)

Thanks in advance for your time and consideration,
Laird