Closed Bug 1777873 Opened 2 years ago Closed 2 years ago

calendar locale

Categories

(Calendar :: General, defect)

Thunderbird 102
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1758739

People

(Reporter: meso5, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Firefox/102.0

Steps to reproduce:

I upgraded to TB v102 and created calendar events as normal.

Actual results:

The date/time format in displayed calendar events follows the US locale, instead of my system locale (GB) that is correctly used for emails on my Windows 10 system. eg 7/13/2022 03:05 PM instead of 13/7/2022 15:05. This is rectified if I change Language in the TB settings to English (GB).

Expected results:

Like email messages and every other application, calendar events should follow the system locale, not the locale used by TB to display its menus etc.

Component: Untriaged → General
Keywords: dupeme
Product: Thunderbird → Calendar
Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Keywords: dupeme
Resolution: --- → DUPLICATE

Please note: What you all "system locale" is officially the "Regional settings locale". You can chose between using it (default) and using the application locale, in your case en-US. Many users of the en-US application prefer to use their local (as in place of residence) locale, for example en-GB, en-AU or even other languages, like de, etc.

This bug has already been reported, see bug 1758739.

I would expect en-US applications to use en-US for the interface (menus etc) and 'Regional settings locale' (en-GB in my case) for data. That's what TB has been doing until recently, and that's what it still does in displaying email messages (the list, headers pane etc). IME, TB's calendar changed in v102 and is now inconsistent with the email part of TB, and every application I am aware of (eg Microsoft Office and Libre Office). At the very least, I think email and calendar in TB should be consistent.

Fully agreed, the functionality you describe existed in TB 91 and before and will need to be re-established in bug 1758739.

You need to log in before you can comment on or make changes to this bug.