Shaun Walker

@zyhfish yes @mdmontesinos already outlined the root cause and a number of solutions earlier in this thread. It appears that although Microsoft said they "fixed" TimeZoneInfo in .NET 6, they...

@mdmontesinos do you want to submit a PR to integrate Nodatime: - list of time zones a user can select should be based on IANA format (retrieved client-side - no...

@mdmontesinos I have finally had time to test the NodaTime changes and unfortunately the results are still not optimal. Specifically, the list of time zones which NodaTime offers are not...

@mdmontesinos thank you for investigating TimeZoneNames and TimeZoneConverter. At this point I am seriously wondering if it makes sense to simply create a static class in Oqtane which contains a...

@mdmontesinos PR #5411 is a proposed solution to the problem discussed above which utilizes the existing Localization infrastructure to solve the problem: - uses NodaTime to retrieve the list of...

@mdmontesinos I am not really happy with any of the solutions so far. It is shocking to think the basic cross platform time zone support is this bad in .NET...

One other option is to simply use the list of time zones supported by NodaTime and make a best effort to convert them into "friendly" names: ``` var timezones =...

In regards to my earlier statement: "For example, do most applications simply obtain the time zone dynamically on the client rather than relying on a specification on the server. If...

@mdmontesinos #5421 offers more improvements to the time zone list: - it filters out time zones which do not have an associated country (this reduces the list by ~120 entries)...

@mdmontesinos Correct, the U.S. time zones do not include a country code - not sure if this is a bug in NodaTime as the TZDB includes a country code for...