Mozilla Destek’te Ara

Destek dolandırıcılığından kaçının. Mozilla sizden asla bir telefon numarasını aramanızı, mesaj göndermenizi veya kişisel bilgilerinizi paylaşmanızı istemez. Şüpheli durumları “Kötüye kullanım bildir” seçeneğini kullanarak bildirebilirsiniz.

Daha Fazlasını Öğren

Thunderbird 102.0.1 regional setting time 24 format not allowed

  • 1 yanıt
  • 1 kişi bu sorunu yaşıyor
  • 1 gösterim
  • Son yanıtı yazan: 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

Tüm Yanıtlar (1)

more options

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