Because jsTimezoneDetect is not very active project I decided to add a workaround on PHP side. Fixed in https://github.com/roundcube/roundcubemail/commit/36485dfc345ad724f08eaa7ea30c3cc88e48a00d.

Copenhagen is, in principle, available. The reason for the parent ticket to exist has largely been obsoleted. This sub-ticket, and its sub-tickets, can therefore be closed.

I have filed now a bug at the jstz library, because I guess that would be the cleanest solution.
If that ignores Etc timezones coming from the internationalization API from the browser, then it calculates a proper Olson timezone.

It does not depend on Windows Server version.
It does not depend on Firefox version either.

I got more details: the client is Firefox 56 running on Windows Server 2012 R2. The timezone setting for the user in Roundcube is "auto".

Done.

https://git.kolab.org/rLKXab256ebd90d3cf7186c44211a40e2602019c67c9

The attach property is indeed optional, but libkolabxml doesn't treat it as optional property.

https://git.kolab.org/rLK65aaf8504a5fd0bc6775ef52686bf1c8a9e3b5bb

This will need to be packaged and tested in a setup where this actually happens.

A patch has been added to libkolab 0.6.3 and libkolab 0.7 (which has never been released apparently).

I was not able to catch this debug information in PHP, I'm not sure it's possible/simple in python. So, my preferred solution would be to fix libkolab/libcalendaring. In my opinion it would be reasonable to get rid of it on packaging level.

D127 together with D123 are fixing unit tests. Now the output is:

[root@kolab pykolab]# nosetests ./tests/unit
...............................Error: /home/abuild/rpmbuild/BUILD/libkolabxml-1.2/src/objectvalidation.cpp 94:   event.start() is not set
Error: /home/abuild/rpmbuild/BUILD/libkolabxml-1.2/src/xcalconversions.h 1500:   Start date is missing, but is mandatory for events
Debug: /home/abuild/rpmbuild/BUILD/libkolabxml-1.2/src/kolabformat.cpp 94:   Error occurred while writing.
.......................unnamed app(16962) KCalCore::ICalFormatImpl::populate: No PRODID property found
unnamed app(16962) KSystemTimeZonesPrivate::readConfig: readConfig(): local zone= "UTC"
unnamed app(16962) KSystemTimeZonesPrivate::readZoneTab: readZoneTab( "/usr/share/zoneinfo/zone.tab" )
.....unnamed app(16962) KCalCore::ICalFormatImpl::populate: No PRODID property found
.....(20:39:09) timezoneconverter.cpp(51):      Guessed timezone and found:  "" 
(20:39:09) commonconversion.cpp(44):    invalid timezone:  "None" , assuming floating time 
.unnamed app(16962) KCalCore::ICalFormatImpl::populate: No PRODID property found
.Error: /home/abuild/rpmbuild/BUILD/libkolabxml-1.2/src/utils.h 114:   bad numeric conversion: negative overflow
Error: /home/abuild/rpmbuild/BUILD/libkolabxml-1.2/src/utils.h 114:   bad numeric conversion: negative overflow
schema exception
:25:25 error: value '' does not match regular expression facet '(\-|\+)?\d{4}\-\d{2}\-\d{2}T\d{2}:\d{2}:\d{2}(\.\d*)?Z?'
Critical: /home/abuild/rpmbuild/BUILD/libkolabxml-1.2/src/xcalconversions.h 1940:   Failed to parse calendar!
Debug: /home/abuild/rpmbuild/BUILD/libkolabxml-1.2/src/kolabformat.cpp 94:   Error occurred while writing.
........................................................................S.
----------------------------------------------------------------------
Ran 140 tests in 2.898s

Hmm... I'm not so sure. According to RFC5545 it is not valid.

Oops. It looks that "P" is valid. I'll look for the issue in other places.

A DateTime class needs to be introduced to replace the date-only functionality provided by KDateTime that is no longer available in QDateTime

The following usecases are currently covered by libkolab:

• Interpretation and expansion of recurrences
• Detection of conflicts in event-sets
• Retrieval of current system-time
• Attendee/Delegation-helpers for events
• iTip/iMip reading/writing
• iCalendar reading/writing
• Conversion between kolab and KDE Containers
• Generating/aggregating and serializing freebusy
• Definitions such as types, used in the kolab MIME-message format and IMAP annotations.
• Reading/writing of kolab objects to/from V3 MIME-messages
• Reading/writing of kolab objects to/from V3 XML
• Reading/writing of kolab objects to/from V2 MIME-messages
• Reading/writing of kolab objects to/from V2 XML

Everything's medium until product owners say different.

Everything's medium until product owners say different.

Everything's medium until product owners say different.

Everything's medium until product owners say different.

Everything's medium until product owners say different.

Everything's medium until product owners say different.

Everything's medium until product owners say different.

Everything's medium until product owners say different.

Everything's medium until product owners say different.

Dropping QT from libkolab would be a complete rewrite of it, and also mean we no longer use any KDE libraries.

Here too consider using Boost directly, which does provide both a date and a date time facet.

Consider removing the dependency on Qt altogether for this part by using Boost directly, which is more stable and can be ported more easily, reducing the dependency tree.