en-CA) in Weblate #1183

New issue

Open

opened 2026-05-07 00:30:53 +02:00 by BreizhHardware · 2 comments

BreizhHardware commented

2026-05-07 00:30:53 +02:00

Owner

Originally created by @usefulish on GitHub (Apr 14, 2026).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1702

Hi,

I noticed that ntfy currently only exposes a single English locale (effectively en-US) in the web UI, which results in US-style date/time formatting.

While looking into translations in Weblate, I saw that several English locale variants already exist, including:

en-001 (World / International English)
en-GB
en-CA

However, these do not appear to be enabled for the ntfy project (Weblate only allows selecting “basic languages”).

Would it be possible to enable these existing English locales for the web UI?

This would allow users to select an English variant that better matches their local formatting expectations, without introducing a separate date/time formatting setting.

For example, this would allow English UI without forcing US date formatting.

Thanks!

Originally created by @usefulish on GitHub (Apr 14, 2026). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1702 Hi, I noticed that ntfy currently only exposes a single English locale (effectively en-US) in the web UI, which results in US-style date/time formatting. While looking into translations in Weblate, I saw that several English locale variants already exist, including: - en-001 (World / International English) - en-GB - en-CA However, these do not appear to be enabled for the ntfy project (Weblate only allows selecting “basic languages”). Would it be possible to enable these existing English locales for the web UI? This would allow users to select an English variant that better matches their local formatting expectations, without introducing a separate date/time formatting setting. For example, this would allow English UI without forcing US date formatting. Thanks!

BreizhHardware added the

enhancement

label

2026-05-07 00:30:53 +02:00

BreizhHardware commented

2026-05-07 00:30:54 +02:00

Author

Owner

@binwiederhier commented on GitHub (Apr 14, 2026):

There are definitely languages with different variants:

./app/src/main/res/values-pt-rBR/strings.xml
./app/src/main/res/values-pt/strings.xml

I was able to add en_GB, https://hosted.weblate.org/projects/ntfy/android/en_GB/ -- You should be able to add your own languages.

@binwiederhier commented on GitHub (Apr 14, 2026): There are definitely languages with different variants: ``` ./app/src/main/res/values-pt-rBR/strings.xml ./app/src/main/res/values-pt/strings.xml ``` I was able to add en_GB, https://hosted.weblate.org/projects/ntfy/android/en_GB/ -- You should be able to add your own languages. <img width="1539" height="957" alt="Image" src="https://github.com/user-attachments/assets/b88fbc7b-7b69-41c7-bf4b-ca854f3fed7b" />

BreizhHardware commented

2026-05-07 00:30:54 +02:00

Author

Owner

@usefulish commented on GitHub (Apr 14, 2026):

Thanks! My issue is specifically with the web UI date formatting rather than Android.

I can see en_GB on the Android component now. Would it be possible to enable en_GB (and ideally en_CA / en_001 if you’re open to it) for the web component as well?

That would let me test whether one of those English variants solves the date formatting issue there without needing any code changes.

@usefulish commented on GitHub (Apr 14, 2026): Thanks! My issue is specifically with the web UI date formatting rather than Android. I can see en_GB on the Android component now. Would it be possible to enable en_GB (and ideally en_CA / en_001 if you’re open to it) for the web component as well? That would let me test whether one of those English variants solves the date formatting issue there without needing any code changes.