Comments for pscal
Re: pscal's output broken beginning in 2009
> The calendars produced beginning in 2009
> are off by one day. For example,
> 2008-12-31 and 2009-01-01 are both on
> Wednesday.
Ouch. The problem I ran into above wasn't for the latest release. However, there does appear to be another LANG-related problem for some users. (Different than the older comment regarding the LANG setting.) "en_US" isn't recognized as a valid language setting; at least not on SuSE-based systems or even an old RH8.0 I have access to. Changing the assignment on line 127 to "en_US.UTF-8" fixes that problem. Prefixing a recognized LANG setting to the command (i.e., "LANG=C pscal mm yyyy") works, too.
pscal's output broken beginning in 2009
The calendars produced beginning in 2009 are off by one day. For example, 2008-12-31 and 2009-01-01 are both on Wednesday. I hope this can be fixed as pscal has been so useful over the years.
Bug in 1.11 -- checking against POSIX LANG values falls short
First, the SYNOPSIS in the comments at the start of the script is utterly outdated. Anyhow...
The default setting of LANGUAGE picks up $LANG from the environment, but then doesn't test for the POSIX "sublanguage" strings. For example, en_US (American English) is the default LANG setting in all of our systems out of the box, but pscal warns about an unknown language. (It tests for "en", but nothing more.)
Unfortunately, warning isn't enough, because it generates bad PostScript as output.
Anyhow, it's good to see that someone is maintaining pscal. It's been so useful over the years!
Sunrises and sunsets in the calendar
There are scripts for put sunrises and sunsets into calendar.
github.com/gcb/pscal/t...
i'm sending patches and inviting people to commit their holiday files here.
also will try to extract the holidays automatically from google calendar