[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    Re: [Kde-pim] RFC2822 interpretation
From:       Ingo =?utf-8?q?Kl=C3=B6cker?= <kloecker () kde ! org>
Date:       2005-12-01 21:58:27
Message-ID: 200512012258.28713 () erwin ! ingo-kloecker ! de
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Wednesday 30 November 2005 20:41, Jose M. Prieto wrote:
> El Martes, 29 de Noviembre de 2005 22:22, Ingo Klöcker escribió:
> > IOW, we should try to guess the correct time zone from other
> > information (e.g. the first Received header). Currently we don't do
> > this in KMail. In fact we are using KRFCDate::parseDate() from
> > kdelibs. And this one doesn't seem to handle "-0000" other than
> > "+0000".
>
> I don't think so.
>
> From the RFC:
>    The form "+0000" SHOULD be used to indicate a time zone at
>    Universal Time.  Though "-0000" also indicates Universal Time, it
> is used to indicate that the time was generated on a system that may
> be in a local time zone other than Universal Time and therefore
> indicates that the date-time contains no information about the local
> time zone.
>
> With "+0000" you know that the date-time is expressed in UTC *and* it
> has been generated in a system running in UTC time zone.
>
> With "-0000" you also know that the date-time is expressed in UTC,
> *but* it may have been generated in a system running in a different
> time zone.

D. J. Bernstein seems to use "-0000" with this intention (at least on 
the ietf-822 mailing list). This is a strong indication for your 
interpretation to be the intended interpretation. In particular, 
KRFCDate::parseDate seems to behave correctly.

Regards,
Ingo

[Attachment #5 (application/pgp-signature)]

_______________________________________________
kde-pim mailing list
kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/

[prev in list] [next in list] [prev in thread] [next in thread]