Torsten Wagner writes: > I did not had time to play with the different parameters. For now I simply > added all of them. > I guess it has to do either with the timezone or with the daylight settings. > Maybe you want to add this to a "How-to install for SOGo" as a workaround.
I think I found a better solution. I pushed a change to org-caldav which allows to set org-icalendar-timezone to the string "UTC", which will put events using universal time. The server should then transpose it to the timezone you have set in your SOGo preferences. It works for me (for SOGo, mind you; other calendar servers don't work well with that). > One problem remain. If I change something in the caldav calendar, the time > information in org get lost completely. > E.g. > * Meeting <2013-01-16 Wed 14:00> > becomes > * Meeting > It subsitutes the right entry and hence I believe it gets the ID stuff right. > However, it seems to have trouble to interpret the time information right (and > ignore them?). > If there is a way to help you debugging this please let me know. My test suite runs fine with the SOGo server, so I'm guessing it has to do with how you format your entries. Does this also happen when you put the timestamp underneath the heading? On a general note, I find manipulating Org entries rather delicate and wonder why there are no helper functions to change things like headings, timestamps, etc., which take care of the multitude of possibilities how entries can be formatted. My guess is that org-elements might be the solution for this, but I haven't looked at it yet... -David
