Join us and the lead editor of IRL, Mozilla's multi-award-winning podcast, for a behind-the-scenes look at the pod and to contribute your ideas for the next season, themed: "AI and ME." Mark your calendar and join our Community Call on Wednesday, Aug 7, 17:00–17:45 UTC. See you there!

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Thunderbird 102.0.1 regional setting time 24 format not allowed

  • 1 回覆
  • 1 有這個問題
  • 1 次檢視
  • 最近回覆由 david

more options

I´m using TB 102.0.1 in Windows x64 Professional. I have config TB to work in English (menus, notifications, etc.), but with this update I have to change to Spanish language to allow the 24h format in Calendar. Every time I change to the Regional setting (Spanish) from an English language the Calendar change to AM/PM format, when I have config Windows to 24h format (HH:mm). I have always config TB to work with English menus, but I lost this possibility with the last update. Windows 7 Professional work with an Spanish language installation, and I suppose that in this new version of TB something has change with the Language/regional configurations. Is there any possibility to select the "time format" of the Calendar (24h to AM/PM or AM/PM to 24h)? Thanks

I´m using TB 102.0.1 in Windows x64 Professional. I have config TB to work in English (menus, notifications, etc.), but with this update I have to change to Spanish language to allow the 24h format in Calendar. Every time I change to the Regional setting (Spanish) from an English language the Calendar change to AM/PM format, when I have config Windows to 24h format (HH:mm). I have always config TB to work with English menus, but I lost this possibility with the last update. Windows 7 Professional work with an Spanish language installation, and I suppose that in this new version of TB something has change with the Language/regional configurations. Is there any possibility to select the "time format" of the Calendar (24h to AM/PM or AM/PM to 24h)? Thanks

所有回覆 (1)

more options

This is a known bug and should be resolved in a future release.