all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Antoine Beaupré" <anarcat@debian.org>
Cc: 53396@debbugs.gnu.org
Subject: bug#53396: 27.1; icalendar rendering should include timezone
Date: Fri, 21 Jan 2022 11:16:18 +0100	[thread overview]
Message-ID: <874k5xv1fx.fsf@gnus.org> (raw)
In-Reply-To: <87tudyb2lh.fsf@curie.anarc.at> ("Antoine Beaupré"'s message of "Thu, 20 Jan 2022 14:59:22 -0500")

> 2022/1/25 13:00-14:00 Next team meeting
>  Organizer: mailto:user@example.org
> 
> After:
> 
> 2022/1/25 13:00-0500 - 14:00-0500 Next team meeting
>  Organizer: mailto:user@example.org

That looks very confusing, I think -- I first read that as a
mis-formatted time range from 13:00 to 05:00.  

If we want to include the time zone in the display, it shouldn't be
appended to both the start and end times (it's unlikely that they're in
different time zones), and it should be formatted in a different, less
ambiguous way, but I'm not sure how.

And if it's in the local time zone, it probably shouldn't be included at
all.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no






  reply	other threads:[~2022-01-21 10:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-20 19:59 bug#53396: 27.1; icalendar rendering should include timezone Antoine Beaupré
2022-01-21 10:16 ` Lars Ingebrigtsen [this message]
2022-01-21 14:33   ` Antoine Beaupré
2022-01-22 11:29     ` Lars Ingebrigtsen
2022-01-23 21:04       ` Antoine Beaupré
2022-01-24  9:41         ` Lars Ingebrigtsen
2022-06-07 22:04 ` Stefan Kangas
2022-06-08  2:37   ` Eli Zaretskii
2022-06-08 13:20     ` Antoine Beaupré
2022-06-08 14:19       ` Eli Zaretskii
2022-06-08 15:33         ` Antoine Beaupré
2022-06-13 12:11     ` Stefan Kangas
2022-06-11 17:08   ` Alexander Adolf

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=874k5xv1fx.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=53396@debbugs.gnu.org \
    --cc=anarcat@debian.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.