[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#273350: marked as done (icalendar import - case-sensitive)

Your message dated Mon, 19 Feb 2007 18:29:27 +1100
with message-id <200702191829.27323.jiri@baum.com.au>
and subject line Close: Bug#273350: icalendar import - case-sensitive
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: korganizer
Version: 4:3.2.2-2

When opening iCalendar files generated by other applications, korganizer is 
case-sensitive in the property names (eg VERSION, DTSTART), parameter names 
(eg VALUE) and enumerated parameter values (eg DATE).

RFC 2445, section 4.1 specifies "All names of properties, property parameters, 
enumerated property values and property parameter values are 
case-insensitive."

For example, if the VERSION property of the calendar is written
Version:2.0
korganizer will refuse to open the file.

If the DTSTART property of an event is written
dtStart:20040926
or
DTSTART;VALUE=date:20041009
korganizer will discard the event.

If the DTSTART property of and event is written
DTSTART;value=DATE:20040926
korganizer will crash.

Workaround: write names of properties, property parameters and evaluated 
values in upper case.

Suggested solution: make the parser more robust (so it doesn't crash), and 
make it case-insensitive where required by the RFC.

Jiri
-- 
Jiri Baum <jiri@baum.com.au>

--- End Message ---
--- Begin Message --- 
Hello,

> We (the Debian Qt/KDE team) are trying to update the bug status of some
> old bugs in the BTS.

This bug appears to have been fixed at some stage; the examples given in my 
report now import without problem in the current "testing" version (3.5.5).

I didn't notice when - as the author of an icalendar data source, I simply 
changed all the keywords to uppercase and paid it no more attention...


Jiri
-- 
Jiri Baum <jiri@baum.com.au>                   http://www.baum.com.au/~jiri

--- End Message ---
Reply to: