From: Adam Spiers <orgmode@adamspiers.org>
To: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: .ics export violates RFC2445
Date: Wed, 7 Nov 2007 20:56:21 +0000 [thread overview]
Message-ID: <20071107205621.GT13544@atlantic.linksys.moosehall> (raw)
I use org-export-icalendar-combine-agenda-files to export my
appointments to an .ics file which I point korganizer at.
I noticed ages ago that if I have an appointment with a comma in, e.g.:
** <2007-12-07 Fri 20:00> foo, bar
korganizer always shows it as "bar" rather than "foo, bar". But I
never got round to investigating whether it was a bug with the export
or korganizer or something else ... until now :-) I just took a quick
look at the iCalendar spec, which is RFC2445, and discovered that the
SUMMARY field is defined as follows
summary = "SUMMARY" summparam ":" text CRLF
-- from http://tools.ietf.org/html/rfc2445#section-4.8.1.12
And the definition of 'text' in this context explicitly states that
several characters, including commas, need to be escaped with a
backslash:
http://tools.ietf.org/html/rfc2445#section-4.3.11
Sure enough, when I edited the .ics file and manually escaped the
comma, korganizer displayed the summary correctly.
next reply other threads:[~2007-11-07 20:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 20:56 Adam Spiers [this message]
2007-11-10 10:07 ` .ics export violates RFC2445 Carsten Dominik
2008-04-29 14:12 ` Adam Spiers
2008-04-29 15:52 ` Carsten Dominik
2008-04-29 17:16 ` Adam Spiers
2008-05-15 8:33 ` Carsten Dominik
2008-05-27 21:55 ` Adam Spiers
2008-05-27 22:25 ` 1-way syncing with google calendar (was Re: .ics export violates RFC2445) Adam Spiers
2008-05-28 21:02 ` Cezar Halmagean
2008-05-28 21:57 ` Adam Spiers
2008-05-29 10:32 ` Tim O'Callaghan
2008-05-29 13:08 ` Re: 1-way syncing with google calendar David Smith
2008-05-30 20:55 ` Adam Spiers
2009-03-20 15:18 ` David Abrahams
2008-04-30 18:38 ` .ics export violates RFC2445 Leo
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=20071107205621.GT13544@atlantic.linksys.moosehall \
--to=orgmode@adamspiers.org \
--cc=emacs-orgmode@gnu.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).