Always write both DAYLIGHT and STANDARD periods to VTIMEZONE blocks. #11
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…because Outlook only looks at the STANDARD.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Outlook apparently only looks at the STANDARD portion of the VTIMEZONE block. If it doesn't exist, Outlook can't figure out the offsets for the timezone and defaults them to 0. Then Outlook thinks that the local time for the event is many hours off from what it really is. Stoopid Outlook! (Specifically, Outlook 2011 for Mac. I don't have access to any other versions for testing.)
If we put both DAYLIGHT and STANDARD blocks in, the Outlook parses the timezone without problems.