Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recommended format for listing times in multiple timezones #1126

Open
cmaimone opened this issue Apr 14, 2023 · 4 comments
Open

Recommended format for listing times in multiple timezones #1126

cmaimone opened this issue Apr 14, 2023 · 4 comments

Comments

@cmaimone
Copy link
Contributor

We recommend in docs/events.md that people list times for events in multiple timezones. The question is about what format to recommend.

Current example is: 12ET/11CT/10MT/9PT

One recommendation is for some spacing, and adding full time zone designation: 12pm EDT/11am CDT/10am MDT/9am PDT

However this format can lead to people reading "EDT/11am" as the unit of info, instead of "12pm EDT" as the unit of info

@mtbc
Copy link
Contributor

mtbc commented Apr 14, 2023

My main suggestion is we don't adopt, say, "11 PM PT" because the jumble of two-capital-letters gets hard to parse at a glance. Not sure if "11 pm PT" or "11 PM PDT" or suchlike may be preferable. @danielskatz, any thoughts? I'm okay with simply 11PT too, I guess am/pm is typically obvious?

Could separate with ", " instead of "/" if that helps.

@danielskatz
Copy link
Contributor

I like specifying am/pm (except at 12, when I prefer 12 noon), since some of our events may be of interest to people outside the US, but if others think this isn't needed, ok.

I agree that the slashes are problematic and commas would be better, so I would suggest either
12 noon EDT, 11 am CDT, 10 am MDT, 9 am PDT
or
12 EDT, 11 CDT, 10 MDT, 9 PDT

@mtbc
Copy link
Contributor

mtbc commented Apr 14, 2023

Perhaps we can reach a happy consensus with the former. Let's see what others think.

@kescobo kescobo added the design label Jun 13, 2023
@kescobo
Copy link
Contributor

kescobo commented Jun 13, 2023

Coming in late, it seems like there's some consensus here? Have people been following this guidance?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants