9381 – ical import fail if there is BOM

ical import fail if there is BOM

Status:

CLOSED: WONTFIX

Priority:
Medium

Severity:
normal

Product:
Orage

Component:

general

Comments

Description Volker 2012-10-18 11:40:58 CEST

Hallo,

the ical import of Orage 4.8.3 work fine as long as the file doesn't contain BOM.
But the import fail as soon as the file contain BOM (Byte Order Mark).
You can check this bug with every ical file. Just open it with an editor and save it once with BOM and once without BOM.

Regards,
Volker

Comment 1 juha editbugs

2012-10-18 12:22:11 CEST

Could you give an example of such failing file.
I have no idea what BOM is :) .

Comment 2 Volker 2012-10-18 13:56:50 CEST

Created attachment 4669 
with BOM

Comment 3 Volker 2012-10-18 13:57:17 CEST

Created attachment 4670 
without Bom

Comment 4 Volker 2012-10-18 13:59:50 CEST

I added 2 samples. One with and one without BOM.
You can normaly set that BOM setting in your editor. For example with Editor Kate it is Kate -> Extra -> BOM. (Maybe phrases are a bit different. I traslated from german strings.)

Comment 5 juha editbugs

2012-10-18 14:22:02 CEST

Thanks.
I see with od that there indeed is 3 bytes more in the BOM version.
I use vi editor and have never run into such.

Need to look this a bit.

Comment 6 juha editbugs

2013-11-29 09:48:12 CET

libical takes care of opening the files, so Orage can not do anything to fix this.
It is easiest to convert those files so that they do not contain the BOM mark.

Bug #9381

Reported by:
Volker

Reported on: 2012-10-18
Last modified on: 2013-12-11

People

Assignee:
juha

CC List:
0 users

Version

Version:
4.8

Target Milestone:
---

Attachments

with BOM (419 bytes, text/calendar) 2012-10-18 13:56 CEST , Volker	no flags
without Bom (416 bytes, text/calendar) 2012-10-18 13:57 CEST , Volker	no flags

Additional information