Bug 143467 - Encoding issues when importing calenders from drupal site
Summary: Encoding issues when importing calenders from drupal site
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-25 21:52 UTC by Anders Lund
Modified: 2017-01-07 22:11 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Anders Lund 2007-03-25 21:52:17 UTC
Version:           3.5.6 (using KDE 3.5.6, Kubuntu (feisty) 4:3.5.6-0ubuntu9)
Compiler:          Target: x86_64-linux-gnu
OS:                Linux (x86_64) release 2.6.20-9-generic

When I add a calender from a drupal driven site (exported by drupal's event module) the encoding in korganizers views is wrong.

It looks like misencoded emails, with strings like '=C3=A6' representing the danish letter 'æ' for example.

You can see the file here: webcal://www.fjellebroen-sejlklub.dk/event/ical
Comment 1 Anders Lund 2007-03-25 21:59:52 UTC
As you can see, the calendar contains the correct information about the encoding in every single data where it is required:

SUMMARY;ENCODING=QUOTED-PRINTABLE:Sv=C3=B8mmepr=C3=B8ve
DESCRIPTION;ENCODING=QUOTED-PRINTABLE:<p>Arrang=C3=B8r\:<br />=0D=0A Ungdomsafdelingen</p>=0D=0A
Comment 2 Christoph Kaulich 2009-01-07 11:43:20 UTC
I have the same, using Groupdav with egroupware, containing linebreaks and german Umlaute, which are not handeld correct, using KOrganizer Vers 4.2 beta 2
Comment 3 Denis Kurz 2016-09-24 18:46:21 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 22:11:24 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.