February.
If you do a web search for "lionheart crowned" you'll get lots of
conflicting information. Some sites say 3rd September, while others
say 27th February. Most of the "27th February" crowd seem to take their
information from other incarnations of this file on other operating
systems.
After a very pleasant afternoon spent lunching with my girlfriend's
parents, I availed myself of their extensive reference library.
You'd be surprised how hard it is to get concrete information about this.
The _Encyclopedia Brittanica_ doesn't mention the date, only the year, as
does _Brewer's Dictionary of Phrase and Fable_, as do all the other printed
sources I tried. One of them even said July 7th 1189! Microsoft's (yeah,
so sue me) Encarta '95 has quite a comprehensive entry, but again, no
day and month information
In desperation, I tried the web once more, and finally stumbled upon
http://www.btinternet.com/~timeref/hsttime2.htm. This revealed that
Henry II died on 6th July 1189 (presumably the source of the 7th July
entry in another reference), and that Richard was crowned on 3rd
September.
Best of all, this site gives references. So if any of you have a copy of
_The Life and Times of Richard I_, John Gillingham, pub. George Weidenfeld
and Nicholson Limited, 1974, then you can confirm this for yourselves.
For completenesses sake, I tried to find an ISBN number for the above
book. But Amazon and Barnes and Noble don't appear to stock it (although
it looks like a revised version, by the same author, is due out in October
1999, in case anyone's interested).
PR: docs/10488
Submitted by: solon@macaulay.demon.co.uk
Remove some whitespace
Fix a problem where any event on the Last whatever of the month
was duplicated after the last day of the month (e.g. 32oct.)
PR: 4907
Submitted by: Mikhail Teterin mi@aldan.algebra.com
track.
The $Id$ line is normally at the bottom of the main comment block in the
man page, separated from the rest of the manpage by an empty comment,
like so;
.\" $Id$
.\"
If the immediately preceding comment is a @(#) format ID marker than the
the $Id$ will line up underneath it with no intervening blank lines.
Otherwise, an additional blank line is inserted.
Approved by: bde
o main returns int not void
o use return 0 at end of main when needed
o use braces to avoid potentially ambiguous else
o don't default to type int
o #ifdef 0 -> #if 0
Reviewed by: obrien and chuckr
plain 0 should be used. This happens to work because we #define
NULL to 0, but is stylistically wrong and can cause problems
for people trying to port bits of code to other environments.
PR: 2752
Submitted by: Arne Henrik Juul <arnej@imf.unit.no>
eliminates the "X-authentication-warning" header line that
has been coming out since I made it so that sendmail is
run totally as the user whose calendar file is currently
being processed.
Jan 1st (and probably other dates as well) for some variable
events. E.g.
01/SunThird whatever...
Was being printed as:
Jan 0 Whatever
when calendar was run on January 1st.
Closes PR#2461.
This will make a number of things easier in the future, as well as (finally!)
avoiding the Id-smashing problem which has plagued developers for so long.
Boy, I'm glad we're not using sup anymore. This update would have been
insane otherwise.
calendar -t 0101 -f file
Previously calendar's time processing routine directly
modified the "0101" argument" which confused getopt.
The time routines now make a copy of the argument
to mess with.
E.g. for Easter, and entries like "04/SunFirst" calendar will
now report:
04/05* Good Friday (2 days before easter)
04/07* First Sunday...
instead of:
Easter-2 Good Friday...
04/SunFirst First Sunday...
I also modified the calendar files to use the variable day format
for a lot of events so that they will be reported correctly.
E.g. U.S. daylight savings time is now listed as:
04/SunFirst Daylight savings time...
There are still a lot of wrong dates in there for some events
that move from year to year, but I don't have a good calendar handy
right now that I can use for reference.
