12-hour time format (Canadian localization)

[candideu]

I'd like the option to display time in a 12-hour time format (ex: 3:00pm)

[raphaelm]

just set the "region" of your event to US :)

[candideu]

I'd like this to be set for Canada as well. We also use this format, and my event is in Canada.

[pc-coholic]

Seems to me, like the Canadian Government recommends the 24 hour notation while only discouraging the 12h notation - also matches my personal experience from living in Canada, that the 12 hour system is only used in colloquial usage (and TV announcements), whereas 24 hour syntax is used in official communication.

So for now, selecting Canada as the region will leave things "as is".

But even if your event is in Canada and you set the region to US, nothing bad will happen: as far as I can tell, you'll get exactly what you want: 12 hour display and north-american formatting for numbers, monetary amounts, etc...

[candideu]

Hi @pc-coholic,

The Wikipedia article you linked to cites resources that have been marked by the government as outdated and archived. The up-to-date language tips shared by the government have guidance for both formats. It's really only relevant, as you've said, for official government communication — and even those don't necessarily follow the 24hr time format:

House of Commons (and their official House publications):

Canada Revenue Agency:

National Defence (Military)

Senate of Canada (and the official reports for Senate debates):

---

I was born and raised in Canada, have lived across the country, have worked in government, and speak both French and English fluently. The use of 24h time is really only used by Francophones, who represent 22.8% of the population, and the majority live in the province of Québec. Outside of that, 12hr is more widespread.

I suggest:

• defaulting to 12hr,
• offering both options if "Canada" is selected,
• having a Canadian English region/locale and Canadian French region/locale, or
• rather than having a general "Region" field in the "Localization" tab (which makes it difficult for users to know exactly what formats are being used): why not allow each organizer to select the date display, currency, numbering, and time formats of their choice as separate fields, like Pretix does for customer names?

---

But even if your event is in Canada and you set the region to US, nothing bad will happen: as far as I can tell, you'll get exactly what you want: 12 hour display and north-american formatting for numbers, monetary amounts, etc...

There should be no reason to have to use a different region if "Canada" is on the list.

Additionally, the "Region" field indicates that it's used to set:

• date formatting -- which differs between Canada (day/month/year) and US (month/day/year), and
• "default country for customer addresses" -- which is inconvenient for an in-person event hosted in Canada with attendees who primarily reside in Canada.

I tried to find more documentation for "Region", but didn't have much luck. If this field is also being used for numbers and monetary amounts, as you've stated, that information should also be included in the field's help text.

---

north-american formatting for numbers, monetary amounts, etc...

The formatting for numbers and monetary amounts is different for Canadian French vs Canadian English ("400 000 $" vs "$400,000").

That said, that might have to be a larger discussion on Canadian localization, along with Canadian English spelling (which differs from UK and US English), formal vs informal French, using "tu" vs "vous", etc... For now, I just want a 12hr time format. 😅

[pc-coholic]

This seems like it would end up in a larger discussion what is right and what is wrong, including regional and personal preferences 😬

For the most impact, feel free to file a PR against the django core like it has been done here: django/django#1643

For a more immediate solution that only applies to pretix, you could try patching a en_CA into pretix.helpers.formats., as has been done for pretix.helpers.formats.en_US in your local pretix: https://github.com/pretix/pretix/tree/master/src/pretix/helpers/formats (Just make sure to have provisions for when you update the pretix core...)

But in the bigger picture, I think there needs to be some consent first, what format is the one true one to rule them all... Not to be petty or anything: But I am not sure I have the stamina and/or professional knowledge to give the "win" to anyone at this pint ;-)

[candideu]

For the most impact, feel free to file a PR against the django core like it has been done here: django/django#1643

Will do.

Done: django/django#17794

For a more immediate solution that only applies to pretix, you could try patching a en_CA into pretix.helpers.formats., as has been done for pretix.helpers.formats.en_US in your local pretix: https://github.com/pretix/pretix/tree/master/src/pretix/helpers/formats (Just make sure to have provisions for when you update the pretix core...)

I'm happy to add a patch, but I'm not sure what is meant by "make sure to have provisions" as I'm not familiar with Django. Are there any other files that should be added/edited in pretix core?

See PR: #3844

But in the bigger picture, I think there needs to be some consent first, what format is the one true one to rule them all... Not to be petty or anything: But I am not sure I have the stamina and/or professional knowledge to give the "win" to anyone at this pint ;-)

I don't think it's a matter of winning or losing: just looking for more clarity on what certain fields affect (in this case, "Region"), and giving users options.