After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 455274 - comma-separated CATEGORIES not compatible with iCalendar 2.0 standard
comma-separated CATEGORIES not compatible with iCalendar 2.0 standard
Status: RESOLVED INCOMPLETE
Product: evolution-data-server
Classification: Platform
Component: libical
unspecified
Other Linux
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
evolution[categories]
Depends on:
Blocks:
 
 
Reported: 2007-07-09 20:03 UTC by Patrick Ohly
Modified: 2010-09-04 02:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description Patrick Ohly 2007-07-09 20:03:39 UTC
I got a report that SyncEvolution does not handle CATEGORIES correctly
in ical 2.0 events when multiple categories are specified. It turned out
that Evolution or more likely, libical, import/export such events with
the comma separator escaped like this:
  CATEGORIES:Anniversary\,Holiday

RFC 2445 specifies CATEGORIES with a normal comma as separator and gives
this example:
  CATEGORIES:APPOINTMENT,EDUCATION

When importing such an event, Evolution stores it with two different
category properties and then only uses the later one in the GUI:
  CATEGORIES:APPOINTMENT
  CATEGORIES:EDUCATION

I could reproduce this with Evolution 2.10, but do not have the time to
investigate further.

It's probably obvious, but let me point out that any fix for this needs
to accept both \, and , as separator to remain backwards-compatible with
existing .ics calendar data files. It should use , when writing entries.
Comment 1 Matthew Barnes 2010-06-24 21:54:23 UTC
We don't bundle our own copy of libical anymore.  Is this bug still relevant or should it be moved upstream to the Free Association project?
Comment 2 Tobias Mueller 2010-09-04 02:52:18 UTC
Patrick, I am closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Or better forward it to libical.
Thanks!