Gnus development mailing list
 help / color / mirror / Atom feed
From: Greg Stark <gsstark@MIT.EDU>
Subject: Re: gnus date suggestion
Date: 08 Aug 1997 01:43:52 -0400	[thread overview]
Message-ID: <ycq7mdxtejr.fsf@portB01.Generation.NET> (raw)
In-Reply-To: Stainless Steel Rat's message of 05 Aug 1997 20:52:41 -0400


The dates in messages must be in RFC-822 format, don't be silly.

However, it would be useful for gnus to be able to display the dates in
whatever localized date format the user asked for. I'm not sure if there's a
global handling of localization features or date formatting code yet, if not i
would urge anyone interested in seeing dates in non-american formats to look
at gnus-art.el and timezone.el and write a small package for formatting dates
according to local conventions. 


PS:

someone said:
> When you write `123', you do not ask yourself if `2' is the number of
> hundreds, tens, or units.  Hopefully, many people share this convention
> that going left to right goes from more to less significative.

You must have missed the last twenty years of computer history, ask someone
what the terms "little-endian" and "big-endian" mean. Then ask what byte-order
PDP11 used.


  parent reply	other threads:[~1997-08-08  5:43 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-01-12 19:12 Jason R. Mastaler
1997-01-12 22:07 ` David Moore
1997-01-15  1:09   ` Lars Magne Ingebrigtsen
1997-05-01 14:21   ` Jason R. Mastaler
1997-05-01 21:30     ` François Pinard
1997-05-03  4:17       ` Jason R. Mastaler
1997-05-03 14:53         ` François Pinard
1997-05-03 15:13           ` Hrvoje Niksic
1997-05-03 16:41             ` Lars Magne Ingebrigtsen
1997-05-05  6:45               ` Steinar Bang
1997-05-08 12:39                 ` Lars Magne Ingebrigtsen
1997-05-03 17:31             ` Jason R. Mastaler
1997-08-05 23:07             ` François Pinard
     [not found]               ` <x73eooi146.fsf@peorth.gweep.net>
1997-08-08  5:43                 ` Greg Stark [this message]
1997-05-03 15:35           ` Johan Danielsson
1997-08-05 22:59             ` François Pinard
1997-08-06 23:11               ` Kyle Jones
1997-08-07 16:32                 ` Johan Danielsson
1997-10-21 14:04                 ` François Pinard
1997-10-21 19:03                   ` Jason R Mastaler
1997-10-21 19:59                     ` Valdis.Kletnieks
1998-02-08 19:06                     ` François Pinard
1998-02-08 19:55                       ` Lars Magne Ingebrigtsen
1998-02-08 20:09                       ` Kyle Jones
1998-02-09  1:13                         ` François Pinard
1998-02-09 10:06                           ` Per Abrahamsen
1998-02-09 15:31                           ` Lars Magne Ingebrigtsen
1998-02-08 22:53                       ` Jason R Mastaler
1998-02-09  3:49                       ` Stephen J. Turnbull
1998-02-09 15:49                         ` Lars Magne Ingebrigtsen
1997-05-03  8:14       ` David Moore
1997-05-04  0:00       ` Ken Raeburn
1997-05-02  4:53     ` Paul Graham
1997-05-02  5:17       ` Jason R. Mastaler
1997-05-03  8:19     ` David Moore
1997-05-03  8:40       ` Steven L Baur
1997-05-03  9:15         ` Hrvoje Niksic
1997-05-03  8:58       ` Per Abrahamsen

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

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

  git send-email \
    --in-reply-to=ycq7mdxtejr.fsf@portB01.Generation.NET \
    --to=gsstark@mit.edu \
    /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 NNTP newsgroup(s).