Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Outlook generated timezone can´t be parsed #25

Closed
benjamin79 opened this issue Dec 22, 2018 · 3 comments
Closed

Outlook generated timezone can´t be parsed #25

benjamin79 opened this issue Dec 22, 2018 · 3 comments
Labels

Comments

@benjamin79
Copy link

benjamin79 commented Dec 22, 2018

DTSTART;TZID=W. Europe Standard Time:20181227T130000 or
DTSTART;TZID="W. Europe Standard Time":20181227T130000

leads to

** (MatchError) no match of right hand side value: {:error, "Expected end of input at line 1, column 17"}
    (icalendar) lib/icalendar/util/deserialize.ex:66: ICalendar.Util.Deserialize.parse_attr/2
    (elixir) lib/enum.ex:1899: Enum."-reduce/3-lists^foldl/2-0-"/3

Reason seems to be the missing lookup:
https://github.com/bitwalker/timex/blob/master/priv/standard_to_olson.exs

I´m not sure where and how to do it, but there needs be something like this:
Timex.Timezone.Utils.to_olson("W. Europe Standard ") which replaces it with "Europe/Berlin"

@lpil lpil added the bug label Dec 22, 2018
@ericdude4
Copy link
Contributor

@benjamin79 Thanks for your tip on the standard_to_olson.exs file. This is now supported in #36

@ericdude4
Copy link
Contributor

@lpil I think this issue can be closed

@lpil
Copy link
Owner

lpil commented Sep 5, 2020

Thank you

@lpil lpil closed this as completed Sep 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants