* Nick Dokos <nicholas.do...@hp.com> wrote: > Karl Voit <devn...@karl-voit.at> wrote: > > For me, it was a "no time to work on org - stash it"...
OK. I just wanted to make sure that it *is* on someone's todo list :-) >> * Karl Voit <devn...@karl-voit.at> wrote: >> > >> > * <2012-03-05 08:00-09:00> Wrong: ends up as full day event > > org-agenda-write calls org-export-icalendar which calls > org-print-icalendar-entries > which loops over all the entries and parses them, decomposing them into > timestamps. > Each timestamp is then passed to org-parse-time-string. It's this one that > cannot > handle non-standard formats: it uses a regexp and assumes that all the > matched parts > are going to be in fixed places: > > As to how to fix it, there are several possibilities: > > 1. fix your scripts that produce time stamps to include day-of-week. Sorry, deriving DOW from an arbitrary timestamps from arbitrary data sources is either pretty time consuming (calendar calculations) or simply hard to calculate. Outside Org-mode, DOW is seldom part of time-stamp data :-( > 2. change the callers of org-parse-time-string to make sure that DOW is > included. > There are roughly three dozen callers, so 2. is possible but a pain. Ack. > 3. change just one caller: org-print-icalendar-entries to make sure that DOW > is included. > 3. is simple but ugly as sin, Ouch, ack :-) > 4. change org-parse-time-string to handle a missing DOW. > 4. is the best way to handle it within org. Full ack. > I vote for 1. where *you* have to do all the work ;-) YMMD :-) If my brain would be compatible to ELISP, I'd send a patch. Promised. But I'll take my chance and wait for someone else (you?) implementing 4. to resolve this issue for everybody. I really appreciate every second you guys invest in maintaining Org-mode! -- Karl Voit
