unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Carl Witty <cwitty@newtonlabs.com>
Cc: Guile-Devel <guile-devel@gnu.org>
Subject: Re: Text collation
Date: Tue, 05 Dec 2006 14:29:20 -0800	[thread overview]
Message-ID: <1165357761.21448.171.camel@meteor.newtonlabs.com> (raw)
In-Reply-To: <871wne6ppf.fsf@zip.com.au>

On Wed, 2006-12-06 at 07:41 +1100, Kevin Ryde wrote:
> Carl Witty <cwitty@newtonlabs.com> writes:
> >
> > If I understand correctly, this would make date->julian-day (for
> > instance) convert from Julian calendar dates before 1582 and Gregorian
> > calendar dates after 1582.
> 
> Yes.
> 
> > This is cute, but I don't think it's particularly useful;
> 
> Apart from being what people actually used then!
> 
> > the problem is that the Julian to Gregorian switch
> > lasted for hundreds of years around the world (and, indeed, some
> > churches still use the Julian calendar to determine religious dates), so
> > you can't tell if a date is Julian or Gregorian just by looking at the
> > year.
> 
> Yes, the switch happened at different times, but if you're calling it
> gregorian then it makes some sense to go with the date pope gregory
> signed off on :).  It could get some localization perhaps, though that
> sounds like hard work.  I think the gnu "cal" program does that.

I believe that virtually any program that needs to do date computations
on historical dates will need more support than SRFI-19 provides, no
matter what meaning we assign to "date"s with years before 1582.  If you
consider the small set of Guile users who need to do date computation
for historical dates, and the even smaller set for which "before 1582 is
Julian, after 1582 is Gregorian" is exactly the date semantics they
want, I think it is quite possible that this smaller set is empty: that
nobody would ever correctly use the SRFI-19 "date" type for historical
dates.  (My totally-made-up estimate is that the likelihood of wanting a
split in October 1582  is about the same as the likelihood of wanting
the proleptic Gregorian calendar, which is at least used for ISO 8601;
and that both of these are far more likely than wanting a split which is
automatically computed based on the locale of the user running the
program.)

If it is indeed true that nobody would ever correctly use a
split-at-1582 date type, then the decision should be made on the basis
of the difficulty of implementing, testing, and documenting.  It seems
like implementing and testing the proleptic Gregorian calendar is far
easier than the split-at-1582 calendar, and the difficulty of
documenting either is about even.

> > I would propose leaving the code the way it is now, and changing
> > the note to something like "Note: Dates in this module use the proleptic
> > Gregorian calendar,
> 
> If the srfi author wanted to clarify that then it'd be ok, otherwise
> surely a calendar with at least some sort of historical basis is more
> use.

I note that the SRFI does say "A date is a representation of a point in
time in the Gregorian calendar..."

Carl Witty




_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2006-12-05 22:29 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-19  9:23 Text collation Ludovic Courtès
2006-09-19 22:38 ` Kevin Ryde
2006-10-22 18:33   ` Ludovic Courtès
2006-10-23  2:01     ` Rob Browning
2006-10-23  7:56       ` Ludovic Courtès
2006-10-24  8:37         ` Rob Browning
2006-10-25  8:16           ` Ludovic Courtès
2006-10-25  8:46             ` Rob Browning
2006-10-25 18:40               ` Neil Jerram
2006-10-25 19:55                 ` Rob Browning
2006-10-26  8:47                 ` Ludovic Courtès
2006-11-09  7:44                   ` Ludovic Courtès
2006-11-09 17:43                     ` Rob Browning
2006-11-10 13:39                       ` Ludovic Courtès
2006-11-11 15:17                         ` Neil Jerram
2006-11-20 13:24                         ` Ludovic Courtès
2006-11-21 22:03                           ` Neil Jerram
2006-11-22 13:38                             ` Ludovic Courtès
2006-10-25 18:43           ` Neil Jerram
2006-10-25 19:31             ` Rob Browning
2006-10-25 18:33     ` Neil Jerram
2006-10-26  8:39       ` Ludovic Courtès
2006-11-29 23:08     ` Kevin Ryde
2006-11-30 15:19       ` Ludovic Courtès
2006-12-02 21:56         ` Kevin Ryde
2006-12-04  9:01           ` Ludovic Courtès
2006-12-05  0:20             ` Kevin Ryde
2006-12-05 18:42               ` Carl Witty
2006-12-05 20:41                 ` Kevin Ryde
2006-12-05 22:29                   ` Carl Witty [this message]
2006-12-05  0:38         ` Kevin Ryde
2006-12-02 22:02       ` Kevin Ryde
2006-12-10 12:30       ` Ludovic Courtès
2006-12-11 22:32         ` Kevin Ryde
2006-12-12  8:38           ` Ludovic Courtès
2006-12-12 20:04             ` Kevin Ryde
2006-12-13  9:41               ` Ludovic Courtès
2006-12-31 17:10               ` Neil Jerram
2006-12-15 20:52             ` Kevin Ryde
2006-12-12 19:05     ` Kevin Ryde
2006-12-13  9:14       ` Ludovic Courtès
2006-12-12 19:16     ` Kevin Ryde
2006-12-13  9:20       ` Ludovic Courtès
2006-12-12 21:37     ` Kevin Ryde
2006-12-13  9:28       ` Ludovic Courtès
2006-12-13 20:10         ` Kevin Ryde

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1165357761.21448.171.camel@meteor.newtonlabs.com \
    --to=cwitty@newtonlabs.com \
    --cc=guile-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).