I will change the logic so that DAVdroid creates UIDs with “_” instead of “@”, and file names according to the UID. This should minimize potential problems.
Kolab Now: no group support despite using CATEGORIES?
This might be more a question than an issue, so feel free to point me towards more appropriate communication channels.
I’m a Kolab Now user and would love to use DAVdroid for syncing my contacts, but missing groups stop me from doing this. DAVdroid requires CATEGORIES, but after exporting my address book from the web interface I see them being used with the vCards.
Could you please clarify to me what it is that Kolab Now handles in a non-standard way or why no groups are supported? Thanks.
I have posted a similar question to Kolab Now Support and will report on their answer.
The problem is that there are multiple ways to support “groups”. In vCard4 groups are fully specified. In vCard3 CATEGORIES can be used as groups. However vCard3 does not officially support groups. DAVdroid has complete support for vCard3 and very little vCard4 (only some properties). CATEGORIES from the vCard3 standard are supported by DAVdroid (this is why groups in owncloud work). Kolab Now uses another (valid!) way to support these (from vCard4). We have however alreadly looked at this more closely and it is not trivial to implement this…
Some time DAVdroid will be fully compatible with vCard4 – this is a long time goal of us. So there will be also extended group support in the future. However, if someone is able to make a high quality patch for this, we’d appreciate to merge it to master (but I guess this will require structural changes).
Duplicate of #48