Hiya,

We had a user recently have an error where their TimeZone wasn't recognised even though they're from a European capital city, which prompted me to check the list of aliases generated from the iana database.

The version packaged with Fantom currently was generated back in 2020. I've re-generated the aliases list myself using the buildtz generate aliases function and it's generated twice as many aliases as currently exist in the distribution.

I'm aware that I can deploy the aliases file to our deployment - however if possible I'd like to request that the next official build of Fantom have an updated set of TimeZones and aliases generated for it.

Thanks!

Hi, will the Fantom time zone database be updated in Fantom 1.0.83?

I was really hoping it'd be updated in Fantom 1.0.82 given it, was then, some 5 years old.

I ask because TimeZone.cur() throws an Err in the browser JS when the user is in an unsupported time zone - which usually breaks the web app.

In particular we've had issues with customers in:

• America/Argentina/Salta
• Europe/Sarajevo
• Europe/Zagreb

We could build our own custom version of Fantom from source and deploy to our production environments - but it's not easy and adds complication. An updated Fantom TZ database would make life much easier!

We are looking at an update to the latest (2025c) timezone database. There are several changes to timezones and aliases that we need to understand so we can communicate to the community about it effectively.

@SlimerDude - fyi Salta should already work.

But as we get ready to update to 2025c all those timezones you mentioned should work now. Note that Sarajevo and Zagreb are aliases for Belgrade.