fix to support korganizer #12
Closed
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
ghost
assigned 
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.
Hi,
I encountered some problems concerning korganizer and EXDATE:
My korganizer (version 4.4.11) recognizes EXDATE only if it is explicit typed, eg
EXDATE;VALUE=DATE:20120223
instead of
EXDATE:20120223T000000Z
I don't know how far this is related to Pull-Request #11.
I understand horde as some kind of middleware to glue different components together, so I left the original property in place to achieve maximum compatibility (without violating the rfc as far as I know). I'd be glad if you put this upstream.
Thanks,
Manuel