-
-
Notifications
You must be signed in to change notification settings - Fork 171
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
Problem parsing a file with event recurring on weekdays #165
Comments
If I read the RFC correctly, those blanks are invalid. Could you try with removed blanks? Am 13. Juli 2015 10:26:47 MESZ, schrieb Dmitry Medvinsky notifications@github.com:
|
Yeah, it works if I remove the spaces after commas. I'll try to ask the person who sent me this file how did they obtain it. Does the icalendar follow RFC strictly and I should close this issue, or do you include some workarounds if this is, say, a bug in MS Exchange you want to deal with? |
The information about the source of the ical file would really be interesting. If it's from a widely spread source, we should think about including a workaround. |
OK, I'm awaiting the reply from the original file author. |
The PRODID says this is was created by "Microsoft CDO for Microsoft Exchange", does anyone have access to a Microsoft Exchange Server/Client and can try to reproduce this error? |
Well, I just tried it with MS Exchange 13 using its web interface and the generated event didn't have those spaces in the The original author haven't gotten back to me with the info about the origin of the file though. |
The original author contacted me with the following email:
|
Another one:
|
The offending file:
Trying to parse it:
As you can see, there is only one component:
VTIMEZONE
. TheVEVENT
component is gone.The offending line is:
In particular, it's the
BYDAY=MO, TU, WE, TH, FR
part. If I remove this part, everything is parsed as expected:The text was updated successfully, but these errors were encountered: