Bug 123620

Summary: Properties in iCal files are not properly parsed if they include non-standard parameters
Product: [Unmaintained] kresources Reporter: Ismail Onur Filiz <onurf>
Component: frameworkAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Example email that's not properly parsed
Same email in the original form from the user in bug 117684

Description Ismail Onur Filiz 2006-03-14 16:36:23 UTC
Version:            (using KDE Devel)
Installed from:    Compiled sources
OS:                Linux

Part of the output of the attached email file in KMail, that is related to the ical libraries is:

This event has been published
What: CHARSET=utf-8:Anish Mistry - Security Issues
Where: CHARSET=utf-8:Dreese Lab 113 (Lecture Hall)
Start Time:  2005-04-12 22:00
End Time:  2005-04-12 23:00
Duration:  1 hour

I checked RFC 2445 and it looks like CHARSET is not a standard parameter. Still the behaviour should be ignoring those parameters. Please also see comments in Bug 117684.
Comment 1 Ismail Onur Filiz 2006-03-14 16:38:32 UTC
Created attachment 15113 [details]
Example email that's not properly parsed
Comment 2 Ismail Onur Filiz 2006-03-14 16:41:20 UTC
Created attachment 15114 [details]
Same email in the original form from the user in bug 117684

I am posting the original version too. In this one, '=' signs appear as '=3D'
and then What and Where do not appear at all. Again, I believe ignoring the
properties with unknown values should be default. (Maybe in this one it is
normal though, since ENCODING can't be read)
Comment 3 Reinhold Kainhofer 2006-11-02 19:08:01 UTC
Reassigning all KOrganizer bug reports and wishes to the newly created 
korganizer-devel mailing list.
Comment 4 Christoph Cullmann 2024-08-11 18:08:34 UTC
Dear reporter, the resources handling got redone for KF5 and KF6 based PIM applications.

If you still encounter the issues you had in the past, please report them to the current maintained and updated PIM applications you use

Thanks a lot!