Caută ajutor

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Află mai multe

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

Thunderbird 102.0.1 regional setting time 24 format not allowed

  • 1 răspuns
  • 1 are această problemă
  • 1 vizualizare
  • Ultimul răspuns de 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

Toate răspunsurile (1)

more options

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