Calendar name with non-ASCII chars in it (eg é) breaks CalDav

[frankske]

Server: verified on both 5.0.6 and 5.0.8 (both NE).
Client: Apple iCal (latest updates) and Mulberry (behaviour in Mulberry is slightly different, read on for more info).

How to reproduce:
1) configure some calendars in your Zimbra webinterface, setup your CalDav client, make sure it's working, that you can see al calendars etc.
2) add a new calendar, with a special (non-ASCII) character in it (eg: "test with é").
3) Refresh the calendar list in iCal. ==> It won't show up in iCal (shows up as a calendar with an empty name in Mulberry)

Even worse:

4) Add a few new calendars, without special chars in the name.
5) Refresh the Calendar list ==> They won't show up either in iCal (they do show in Mulberry)

To prove my point:

6) Completely erase all data in your iCal, quit iCal, start it again and recreate the CalDav account. ==> Not a single calendar will show up.

7) Delete the calendar with an accented name in it in your Zimbra interface. Refresh the iCal list ==> They all show up again.

Can anyone confirm this and tell me if there is a fix? Thanks.

PS: Please note that adding UTF-8 data to the content of an appointment does seem to work, shows up fine, the error only happens when the name of the calendar contains non-ASCII chars in it.

[frankske]

Anyone that knows if there is a way around this? Or shall I file a bug?

[dkarp]

Please file a bug.

[frankske]

Bug 30430 РCalendar name with non-ASCII chars in it (eg ̩) breaks CalDav

[JLee]

We had a similar bug earlier (bug 26245) which was fixed for ZCS 5.0.5. Since then iCal had several revision updates, and it looks like iCal 3.0.4 no longer works correctly with encoded URL. I've filed a bug for that on Apple (Bug ID# 6156572). As for mulberry, we don't support it yet and I can't say whether it's a problem with client or server.

[frankske]

JLee, thank you for your feedback. I tried Mulberry as well because I read (in this forum or on the zimbra blog) that MB is the most "standard-compliant" CalDav client out there ...

Thank you for filing the Apple bug. Is there a way for me to track that bug? I am registered in Apple's devel program, but it seems I can only file the bugs I created myself.