Aquileo | Recent changes to bugs

Aquileo | #95 Regression: VTIMEZONE contains a lot of non-used timezone info, what mess with Google Calendar, EWS Calendar, etc ...

2015-06-15T21:30:47.174000Z

status: open --> closed-fixed
Group: -->

Aquileo | #95 Regression: VTIMEZONE contains a lot of non-used timezone info, what mess with Google Calendar, EWS Calendar, etc ...

2015-06-15T21:30:33.194000Z

Fixed in the upcoming 2.0 release.

By default nothing has changed, but now you have a buildtime and a runtime ability
to switch the behavior from exact to inter-operable VTIMEZONEs.

First the buildtime switch. if you want to build libical to use inter-operable VTIMEZONEs
without changing your code, then pass the option -DUSE_INTEROPERABLE_VTIMEZONES=true to cmake.

If you are are forced to use a libical that was built without inter-operable VTIMEZONEs as the default,
then you'll need to call icaltzutil_set_exact_vtimezones_support(1) from your application at runtime.

You can also query the VTIMEZONE "mode" by calling the icaltzutil_get_exact_vtimezones_support() function.

I hope this covers every scenario and now consider this issue closed (well, except for possible silly coding errors I may have made)

Aquileo | #86 libical messes with timezone, affecting other threads

2015-06-02T14:35:45.749000Z

status: open --> closed-fixed
Group: -->

Aquileo | #74 Do not escape double quote character " to \" in iCalendar ou

2014-09-20T14:19:17.616000Z

status: open --> closed-fixed
Group: -->

Aquileo | #98 Windows Crash with UTC Timezons

2014-07-15T22:15:39.750000Z

Frank,
2 things:
1) we moved from sourceforge to github. the new url is github.com/libical/libical
the url for this bug report is now https://github.com/libical/libical/issues/98

2) could you try rebuilding the library. pass the option -DDUSE_BUILTIN_TZDATA=false to cmake then make as normal

Aquileo | #96 TZIDs parameters incorrectly parsed if another parameter follows them

2014-06-03T22:53:37.207000Z

status: open --> closed-fixed
Group: -->

Aquileo | #99 src/libical/sspm.c:706: possible bad use of sizeof ?

2014-06-01T22:03:02.821000Z

status: open --> closed-accepted
Group: -->

Aquileo | #99 src/libical/sspm.c:706: possible bad use of sizeof ?

2014-05-07T01:49:51.163000Z

Here is a patch to resolve this warning. I assume that sspm_header.boundary is a null-terminated string and just use strcmp. If this is not a valid assumption, then the code does need some reworking to store the size of the buffer.

This patch also resolves a similar warning in icaltimezone.c.

Aquileo | #96 TZIDs parameters incorrectly parsed if another parameter follows them

2014-04-22T01:59:18.848000Z

This should be fixed by this patch: https://sourceforge.net/p/freeassociation/patches/47/

Aquileo | src/libical/sspm.c:706: possible bad use of sizeof ?

2014-04-09T09:15:09.717000Z

libical-1.0/src/libical/sspm.c:706:32: warning: 'strncmp' call operates on objects of type 'char' while the size is based on a different type 'char *' [-Wsizeof-pointer-memaccess]

    if(strncmp((line+2),parent_header->boundary,
           sizeof(parent_header->boundary)) == 0){

Suggest code rework.