TimeZoneConverter | Lightweight libraries to convert between IANA Windows

by mj1856 C# Version: 3.3.0 License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(4)Vulnerabilities Install Support

kandi X-RAY | TimeZoneConverter Summary

TimeZoneConverter is a C# library. TimeZoneConverter has no bugs, it has no vulnerabilities and it has low support. However TimeZoneConverter has a Non-SPDX License. You can download it from GitHub.

Lightweight libraries to convert between IANA, Windows, Rails, and POSIX time zones.

Support

Quality

Security

License

Reuse

Support

TimeZoneConverter has a low active ecosystem.

It has 457 star(s) with 55 fork(s). There are 24 watchers for this library.

It had no major release in the last 12 months.

There are 3 open issues and 74 have been closed. On average issues are closed in 30 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of TimeZoneConverter is 3.3.0

Quality

TimeZoneConverter has 0 bugs and 0 code smells.

Security

TimeZoneConverter has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

TimeZoneConverter code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

TimeZoneConverter has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

TimeZoneConverter releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of TimeZoneConverter

Get all kandi verified functions for this library.

TimeZoneConverter Key Features

No Key Features are available at this moment for TimeZoneConverter.

TimeZoneConverter Examples and Code Snippets

No Code Snippets are available at this moment for TimeZoneConverter.

Community Discussions

Trending Discussions on TimeZoneConverter

IANA to Windows timezone mapping

Datetime Converting two times not equal starting time

Getting 'ITMS-90338: Non-public API usage' and 'ITMS-90809: Deprecated API Usage' upon submitting Xamarin iOS to Apple AppStoreConnect TestFlight

Github Pages cannot find index.html only in some directories

QUESTION

IANA to Windows timezone mapping

Asked 2022-Apr-14 at 15:13

I am trying to understand how to map IANA timezones to Windows timezones. I did see various posts on here about TimeZoneConverter and I started to use it. However, there is one question which I did not find an answer for:

Since Window to IANA timezones are a one-to-many, if we convert from IANA to Windows, is there a chance that the actual offset and DST flag might be wrong. For example, is there a situatation where a Windows timezone covers 2 hours of time while IANA has two different timezones for each of those hours (of the two). This way if we take the IANA for the second hour and convert it to Windows timezone, the actual offset would be different/changes.

It is less important for us to be able to map from IANA -> Windows and then back to IANA to get same timezone name. It is very important that when we do the re-mapping, the actual offsets and DST flags do not change.

Thank you

...

ANSWER

Answered 2022-Apr-14 at 15:13

It is very important that when we do the re-mapping, the actual offsets and DST flags do not change.

That's effectively requiring the Windows database and the IANA database to always be exactly in sync. While I can understand the desire, it's an unrealistic expectation. Aside from anything else, both databases change over time, as governments make changes to their rules. Unless you ensure that you change both versions at exactly the same time (on all machines you use!) there will always be the possibility of discrepancies. That's aside from the actual data being different in the stable state - which also happens.

If you look at the ICU mapping between Windows and IANA zones names (e.g. this copy in the Noda Time repo) you'll see that it's not a 1:1 mapping. A single Windows time zone ID can map to several different IANA IDs, with one (territory 001) being deemed the primary mapping.

I'd expect that for the vast majority of the time, you'll see the same results between the two - but it's definitely not guaranteed for every instant in every time zone.

Source https://stackoverflow.com/questions/71873777

QUESTION

Datetime Converting two times not equal starting time

Asked 2021-Dec-31 at 22:02

I'm using the TimeZoneConverter NuGet package.

The Pacific standart time is use UTC-8

Created a datetime as pacific timezone.
The pacific time converted utc time.
The utc time converted again to pacific timezone. But the result doesnt equal datetime in the first item. Why? Any idea?

...

ANSWER

Answered 2021-Dec-31 at 22:02

I think Caius Jard hits the correct issue on the comment.

Looks like for Pacific Standard Time on 2021, DST started March 14 02:00 AM and ends 7 November 02:00 AM.

TimeZoneInfo.ConvertTimeFromUtc method handles the daylight saving itself. That means, if the Datetime or DateTimeOffset is a DST on Pacific Standard Time, it returns the DST added value (which is 1 hour usually). That's why your pacificTime variable will be {9/1/2021 12:59:00 PM} not {9/1/2021 11:59:00 PM}

If you have to use ConvertTimeFromUtc for your test, it would be better to check first your DateTime or DateTimeOffset is a daylight saving time or not for that specific timezone. You can use TimeZoneInfo.IsDaylightSavingTime method for that which have overloads both DateTime and DateTimeOffset.

Source https://stackoverflow.com/questions/70544933

QUESTION

Getting 'ITMS-90338: Non-public API usage' and 'ITMS-90809: Deprecated API Usage' upon submitting Xamarin iOS to Apple AppStoreConnect TestFlight

Asked 2021-Feb-10 at 10:55

We're receiving the following message upon submitting our Xamarin.Forms iOS app to Apple's TestFlight.

the Message:

Dear Developer,

We identified one or more issues with a recent delivery for your app, "[bundle name]" [bundle version] ([bundle version]). Please correct the following issues, then upload again.

ITMS-90338: Non-public API usage - The app references non-public selectors in [project name]: applicationWillTerminate, fontWeight, newSocketQueueForConnectionFromAddress:onSocket:, setOrientation:animated:, socket:didConnectToHost:port:, socket:didReadPartialDataOfLength:tag:, socket:didReceiveTrust:completionHandler:, socket:didWritePartialDataOfLength:tag:, socket:shouldTimeoutReadWithTag:elapsed:bytesDone:, socket:shouldTimeoutWriteWithTag:elapsed:bytesDone:, socketDidCloseReadStream:, socketDidSecure:, terminateWithSuccess. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/

ITMS-90809: Deprecated API Usage - New apps that use UIWebView are no longer accepted. Instead, use WKWebView for improved security and reliability. Learn more (https://developer.apple.com/documentation/uikit/uiwebview).

Best regards,

The App Store Team

I have looked up the messages and made too many attempts to no avail. I'd appreciate it if someone could help having Apple to accept our submission.

Let me share more details about

the Environment:

This is a Xamarin.Forms app that we build using Azure DevOps's build pipelines (specifically, Xamarin.iOS task version 2.*) and release using Azure DevOps's release pipelines. We release that to Microsoft AppCenter and we then download the *.ipa from there. We submit it to Apple's AppStoreConnect TestFlight using Transporter app on the Mac from Apple's AppStore.

...

ANSWER

Answered 2021-Feb-10 at 02:23

There are two reasons why Apple reject this submitted version.

ITMS-90338: Non-public API usage - The app references non-public selectors in [project name]: applicationWillTerminate, fontWeight, newSocketQueueForConnectionFromAddress:onSocket:, setOrientation:animated:, socket:didConnectToHost:port:, socket:didReadPartialDataOfLength:tag:, socket:didReceiveTrust:completionHandler:, socket:didWritePartialDataOfLength:tag:, socket:shouldTimeoutReadWithTag:elapsed:bytesDone:, socket:shouldTimeoutWriteWithTag:elapsed:bytesDone:, socketDidCloseReadStream:, socketDidSecure:, terminateWithSuccess.

This means that you need to modify the list names of methods with another name, because these names will conflict with the private method names of Apple's system. You need to find them and replace them with other names.

ITMS-90809: Deprecated API Usage - New apps that use UIWebView are no longer accepted. Instead, use WKWebView for improved security and reliability.

Starting in April 2020, Apple will reject apps that still use the deprecated UIWebView API. While Xamarin.Forms has switched to WKWebView as the default, there is still a reference to the older SDK in the Xamarin.Forms binaries. Current iOS linker behavior does not remove this, and as a result the deprecated UIWebView API will still appear to be referenced from your app when you submit to the App Store.

A preview version of the linker is available to fix this issue. To enable the preview, you will need to supply an additional argument --optimize=experimental-xforms-product-type to the linker.

Detailed steps can refer to UIWebView Deprecation and Xamarin.Forms.

Source https://stackoverflow.com/questions/66119480

QUESTION

Github Pages cannot find index.html only in some directories

Asked 2020-Dec-19 at 07:00

Update: I got fed up and re-do everything from the ground-up and it fixes itself.

I have a github pages site built with Jekyll and Chirpy theme.

Locally, it runs great.

However when deployed on Github Pages there are a few directories that return the 404 page even though the path is valid and there is an index.html file in it.

Example: https://catmandx.github.io/posts/Wgel-CTF-Writeup/ display normally https://catmandx.github.io/tags/cmc/index.html returns 404 http://127.0.0.1:4000/tags/cmc/index.html display correcly.

I have temporarily make the repo public, it's here: https://github.com/catmandx/catmandx.github.io

I have been banging my head for a few hours now. I have tried committing and pushing again to re-run Actions, manually editing the /tags/cmc/index.html file in the gh-pages branch but nothing works.

This is the _config.yml file, not sure if it helps but here:

...

ANSWER

Answered 2020-Dec-19 at 05:10

You can solve this issue by executing bash tools/init.sh

You will also have to run this init.sh every time there is a category/tag created.

Source https://stackoverflow.com/questions/65366633

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install TimeZoneConverter

This library should be compatible with .NET Standard 1.1 and greater, as well as .NET Framework 3.5 and greater. See the .NET Standard Platform Support Matrix for further details about .NET Standard, and please raise an issue if you encounter any compatibility errors. Some functions, such as TZConvert.GetTimeZoneInfo rely on the underlying TimeZoneInfo object having access to time zone data of the operating system. On Windows, this data comes from the registry and is maintained via Windows Updates. On OSX and Linux, this data comes from a distribution of the IANA time zone database, usually via the tzdata package. If your environment does not have the tzdata package installed, you will need to install it for TZConvert.GetTimeZoneInfo to work correctly. For example, the Alpine Linux Docker images for .NET Core no longer ship with tzdata. See dotnet/dotnet-docker#1366 for instructions on how to add it to your Docker images.
This library should be compatible with .NET Standard 1.3 and greater, as well as .NET Framework 4.5 and greater. See the .NET Standard Platform Support Matrix for further details about .NET Standard, and please raise an issue if you encounter any compatibility errors. Note that TimeZoneConverter.Posix takes a dependency on both TimeZoneConverter and Noda Time.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: