emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Simon Thum <simon.thum@gmx.de>
To: emacs-orgmode <emacs-orgmode@gnu.org>,
	Nicolas Goaziou <n.goaziou@gmail.com>
Subject: iCalendar export problem
Date: Thu, 04 Apr 2013 23:29:26 +0200	[thread overview]
Message-ID: <515DF0B6.2010703@gmx.de> (raw)

Hi all,

I have a strange problem that seems related to the iCalendar exporter.

I have an event which has the date spec

    <2013-02-07 Th 12:00-14:00 +1w>

but shows up on 13:00 my phone calendar (fed by ox-icalendar), CEST. Fun 
thing is, I did not experience lag with other entries.

The org entry becomes:

BEGIN:VEVENT
DTSTAMP:20130207T110000Z
UID:TS1-d36d5eb9-e2db-42a3-866f-7442becadef0
DTSTART:20130207T120000
DTEND:20130207T140000
RRULE:FREQ=WEEKLY;INTERVAL=1
SUMMARY:Brown Bag Meeting
DESCRIPTION:Location: R 103\n\nRecurs: <2013-02-07 Do 12:00 
+1w>–<2013-02-07 Do 14:00 +1w> ...

Another one (shown right this time) is:

BEGIN:VEVENT
DTSTAMP:20130404T150000Z
UID:TS1-441e317c-7b52-4910-bbd3-0949a5c1bdd7
DTSTART:20130404T170000
DTEND:20130404T190000

The difference seems to be the DTSTAMP which is "correctly" aligned with 
DTSTART.

However, that's not what DTSTAMP is for. Actually, it should be set to 
the date-time the export happens. At least, that's what they say:

http://stackoverflow.com/questions/11594921/whats-the-difference-between-created-and-dtstamp-in-the-icalendar-format

Changing that probably does not help my problem, but seems better than 
the cooked-up values now ending up in DTSTAMP. I could not see any other 
candidate problems, though the analysis is weak so far.

Cheers,

Simon

next             reply	other threads:[~2013-04-04 21:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04 21:29 Simon Thum [this message]
2013-04-05 19:31 ` iCalendar export problem Nicolas Goaziou

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=515DF0B6.2010703@gmx.de \
    --to=simon.thum@gmx.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).