Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

Thunderbird 102.0.1 regional setting time 24 format not allowed

  • 1 antwoord
  • 1 heeft dit probleem
  • 1 weergave
  • Laatste antwoord van 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

Alle antwoorden (1)

more options

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