TimeZoneNames | complete source of localized time zone names | Internationalization library

Try This:

In order to import the json files in the typescript, we need to include the json type in the wildcard card module declaration( https://www.typescriptlang.org/docs/handbook/modules.html#wildcard-module-declarations ). Use the below declaration code in the typings.d.ts file to resolve the compilation issue.

I'm having the same problem trying to set to spanish culture, the only temporary solution I found was to replace the validator.methods.date function in jquery.validate.globalize.js

You don't need any extra packages for that scenario, as far as I can see.

• For IANA IDs, just use DateTimeZoneProviders.Tzdb
• For "raw offset" IDs, you can use any time zone provider, asking for an ID of the form "UTC+01:00" etc. (So you'd need to add the "UTC" prefix.)
• For Windows zone mapping, you can use TzdbDateTimeZoneSource.Default to get the default TZDB information, then use the WindowsMapping property to get a WindowsZones object you can use for mapping.

TimeZoneConverter may well be simpler to use for the last bullet point, but it's not required. The IANA IDs it provides should work fine with Noda Time.

TimeZoneNames is more about displaying time zone names to users. If you don't need to do that, you probably don't need the package.

Note that persisting all data as UTC may be a really bad idea - it's hard to tell without knowing more about your application. If you only deal with values in the past, or if they're fixed instants in time, that's fine. But if you're allowing users to schedule future events, I'd store the values that the user gave you. Here's an example of why...

Suppose the user says they want to schedule an event for Europe/Paris at 9am on December 1st 2021. If you convert that to UTC now, you'll end up with 2021-12-01T08:00Z, because the current time zone rules say that Paris will be at UTC+1 in December 2021.

However, it's entirely possible that between now and 2021, France will have changed its time zone rules to be on "permanent daylight time", i.e. UTC+2 all year round. At that point, your UTC value of 2021-12-01T08:00Z would correspond to 10am in Paris on the given date - contrary to what the user specified.

It's fine to convert to UTC as well so that you can create a totally ordered view of the data, so long as you retain enough information to perform that conversion again every time there's new time zone data.

As I say, that may not be an issue for you, but it's worth knowing that the "received wisdom" of "Always store everything in UTC" is really not good advice for all scenarios.

I am facing this issue too, upgrade the Facebook SDK to the latest (Facebook Android SDK 4.35), they have added a workaround for this issue:

Very weird issue...

BTW there is not exception thrown, but an AssertionError who extends from Error.

You can catch it using:

This feature is currently work in progress for Kendo UI for Angular. Current progress demo link.

Here is also link to the issue on GitHub.

The dot isn't a separator, but part of the long datetime format.

The "16. januar 2017. 07.57.17 GMT+1" output you get for the long datetime format of "sr-Latn" locale is composed of (a) "16. januar 2017. long date format, (b) a space separator " ", and (c) "07.57.17 GMT+1" long time format.

Note dateTimeFormats.long = "{1} {0}" is what glues date and time (i.e., space separator), dateFormats.long = "dd. MMMM y." (i.e., there's a dot after year), and timeFormats.long = "HH:mm:ss z" .

The dots used as time separator comes from "timeSeparator": ".".

Having said that, if you believe the dot after year is incorrect OR if the separator should be a comma instead of space, please file a ticket into CLDR: http://unicode.org/cldr/trac/newticket