From: Andreas Schwab <schwab@suse.de>
Cc: raman@users.sf.net, emacs-devel@gnu.org
Subject: Re: Emacs Lisp date/time functions and RFC 3339?
Date: Fri, 10 Nov 2006 13:41:51 +0100 [thread overview]
Message-ID: <jeejsbzd68.fsf@sykes.suse.de> (raw)
In-Reply-To: <m364dn6061.fsf@kfs-l.imdomain.dk> (Kim F. Storm's message of "Fri, 10 Nov 2006 11:55:34 +0100")
storm@cua.dk (Kim F. Storm) writes:
> Andreas Schwab <schwab@suse.de> writes:
>
>> "T. V. Raman" <raman@users.sf.net> writes:
>>
>>> The date/time handling functions in Emacs ---
>>> calendar/time-date.el, together with the primitives for
>>> encode-time and decode-time do not handle this format well, nor
>>> does format-time-string.
>>
>> In which way does format-time-string not handle that format?
>
> E.g. %z => -0800 whereas the rfc requests -08:00
GNU date supports %:z, %::z and %:::z, should be easy to add that to
format-time-string.
> Also for UTC, %z => 0000 whereas the rfc requests Z
If you know that you are formatting UTC you can just put the Z in the
format string. The use of Z for UTC is not mandated.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2006-11-10 12:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 3:34 Emacs Lisp date/time functions and RFC 3339? T. V. Raman
2006-11-09 21:57 ` Edward O'Connor
2006-11-09 23:27 ` Richard Stallman
2006-11-10 2:54 ` T. V. Raman
2006-11-10 15:48 ` Miles Bader
2006-11-10 16:56 ` Nic James Ferrier
2006-11-12 1:53 ` T. V. Raman
2006-11-12 2:52 ` Miles Bader
2006-11-12 19:57 ` T. V. Raman
2006-11-11 2:10 ` Richard Stallman
2006-11-10 10:15 ` Andreas Schwab
2006-11-10 10:55 ` Kim F. Storm
2006-11-10 12:41 ` Andreas Schwab [this message]
2006-11-10 13:28 ` Kim F. Storm
2006-11-10 13:35 ` Andreas Schwab
2006-11-10 14:06 ` Kim F. Storm
2006-11-10 14:33 ` T. V. Raman
2006-11-10 14:32 ` T. V. Raman
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jeejsbzd68.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=emacs-devel@gnu.org \
--cc=raman@users.sf.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).