# Revision history [back]

## The Setup

Sailfish is set up to sync contacts with Nextcloud (12). The contacts originate from Thunderbird/CardBook. Syncing worked fine between NC, Thunderbird and Android.

## The Problems

Many of my contacts don't have surnames or only nicknames. Now, these particular contacts (VCARD 3.0) get messed up by SailfishOS' CardDAV. There are two issues:

1. Say there's a contact named Tony. He has no surname, so his name field looks like this N:;;;; (both FN and NICKNAME say Tony). After syncing the contact to SFOS it will soon be displayed as ;Tony;;;.
This looks like some sort of parsing bug. Editing the entry and removing the semicolons seems to work but it I have seen it also duplicating the ;Tony;;; part, leading to Name fields looking like this: \;Tony\;\;\;;Tony;;;.

2. The adress book uses categories for grouping. Although those categories do not show up in the SFOS contacts app (not yet supported?), they are parsed once a contact is edited on the phone. If the contacts category has an Umlaut, say ö, SFOS turns it into some unreadable character (displayed as À + an unknown-character box). I can not fix it other than deleting the contact.
This wrongly encoded character completely knocks out Thunderbird/CardDAV (makes the CPU go haywire) _and_ prevents Nextcloud from parsing the contacts at all!
This looks like Unicode is not correctly implemented in the parser.

In combination with 1., 2. is very annoying since removing the semicolons from the contact will always result in a corrupted contact

## The Setup

Sailfish is set up to sync contacts with Nextcloud (12). The contacts originate from Thunderbird/CardBook. Syncing worked fine between NC, Thunderbird and Android.

## The Problems

Many of my contacts don't have surnames or only nicknames. Now, these particular contacts (VCARD 3.0) get messed up by SailfishOS' CardDAV. There are two issues:

1. Say there's a contact named Tony. He has no surname, so his name field looks like this N:;;;; (both FN and NICKNAME say Tony). After syncing the contact to SFOS it will soon be displayed as ;Tony;;;.
This looks like some sort of parsing bug. Editing the entry and removing the semicolons seems to work but it I have seen it also duplicating the ;Tony;;; part, leading to Name fields looking like this: \;Tony\;\;\;;Tony;;;.

2. The adress book uses categories for grouping. Although those categories do not show up in the SFOS contacts app (not yet supported?), they are parsed once a contact is edited on the phone. If the contacts category has an Umlaut, say ö, SFOS turns it into some unreadable character (displayed as À + an unknown-character box). I can not fix it other than deleting the contact.
This wrongly encoded character completely knocks out Thunderbird/CardDAV (makes the CPU go haywire) _and_ prevents Nextcloud from parsing the contacts at all!
This looks like Unicode is not correctly implemented in the parser.

In combination with 1., 2. is very annoying since removing the semicolons from the contact will always result in a corrupted contact

## The Setup

Sailfish is set up to sync contacts with Nextcloud (12). The contacts originate from Thunderbird/CardBook. Syncing worked fine between NC, Thunderbird and Android.

## The Problems

Many of my contacts don't have surnames or only nicknames. Now, these particular contacts (VCARD 3.0) get messed up by SailfishOS' CardDAV. There are two issues:

1. Say there's a contact named Tony. He has no surname, so his name field looks like this N:;;;; (both FN and NICKNAME say Tony). After syncing the contact to SFOS it will soon be displayed as ;Tony;;;.
This looks like some sort of parsing bug. Editing the entry and removing the semicolons seems to work but it I have seen it also duplicating the ;Tony;;; part, leading to Name fields looking like this: \;Tony\;\;\;;Tony;;;.

2. The adress book uses categories for grouping. Although those categories do not show up in the SFOS contacts app (not yet supported?), they are parsed once a contact is edited on the phone. If the contacts category has an Umlaut, say ö, SFOS turns it into some unreadable character (displayed as À + an unknown-character box). I can not fix it other than deleting the contact.
This wrongly encoded character completely knocks out Thunderbird/CardDAV (makes the CPU go haywire) _and_ prevents Nextcloud from parsing the contacts at all!
This looks like Unicode is not correctly implemented in the parser.

In combination with 1., 2. is very annoying since removing the semicolons from the contact will always result in a corrupted contact

## The Setup

Sailfish is set up to sync contacts with Nextcloud (12). The contacts originate from Thunderbird/CardBook. Syncing worked fine between NC, Thunderbird and Android.

## The Problems

Many of my contacts don't have surnames or only nicknames. Now, these particular contacts (VCARD 3.0) get messed up by SailfishOS' CardDAV. There are two issues:

1. Say there's a contact named Tony. He has no surname, so his name field looks like this N:;;;; (both FN and NICKNAME say Tony). After syncing the contact to SFOS it will soon be displayed as ;Tony;;;.
This looks like some sort of parsing bug. Editing the entry and removing the semicolons seems to work but it I have seen it also duplicating the ;Tony;;; part, leading to Name fields looking like this: \;Tony\;\;\;;Tony;;;..
Update: VCard 4.0 seems not to be affected

2. The adress book uses categories for grouping. Although those categories do not show up in the SFOS contacts app (not yet supported?), they are parsed once a contact is edited on the phone. If the contacts category has an Umlaut, say ö, SFOS turns it into some unreadable character (displayed as À + an unknown-character box). I can not fix it other than deleting the contact.
This wrongly encoded character completely knocks out Thunderbird/CardDAV (makes the CPU go haywire) _and_ prevents Nextcloud from parsing the contacts at all!
This looks like Unicode is not correctly implemented in the parser.parser.
Update: Happens independently of VCard version

In combination with 1., 2. is very annoying since removing the semicolons from the contact will always result in a corrupted contact

## The Setup

Sailfish is set up to sync contacts with Nextcloud (12). The contacts originate from Thunderbird/CardBook. Syncing worked fine between NC, Thunderbird and Android.

## The Problems

Many of my contacts don't have surnames or only nicknames. Now, these particular contacts (VCARD 3.0) get messed up by SailfishOS' CardDAV. There are two issues:

1. Say there's a contact named Tony. He has no surname, so his name field looks like this N:;;;; (both FN and NICKNAME say Tony). After syncing the contact to SFOS it will soon be displayed as ;Tony;;;.
This looks like some sort of parsing bug. Editing the entry and removing the semicolons seems to work but it I have seen it also duplicating the ;Tony;;; part, leading to Name fields looking like this: \;Tony\;\;\;;Tony;;;.
Update: VCard 4.0 seems not to be affected

2. The adress book uses categories for grouping. Although those categories do not show up in the SFOS contacts app (not yet supported?), they are parsed once a contact is edited on the phone. If the contacts category has an Umlaut, say ö, SFOS turns it into some unreadable character (displayed as À + an unknown-character box). I can not fix it other than deleting the contact.
This wrongly encoded character completely knocks out Thunderbird/CardDAV (makes the CPU go haywire) _and_ prevents Nextcloud from parsing the contacts at all!
This looks like Unicode is not correctly implemented in the parser.
Update: Happens independently of VCard version

In combination with 1., 2. is very annoying since removing the semicolons from the contact will always result in a corrupted contact

## The Setup

Sailfish is set up to sync contacts with Nextcloud (12). The contacts originate from Thunderbird/CardBook. Syncing worked fine between NC, Thunderbird and Android.

## The Problems

Many of my contacts don't have surnames or only nicknames. Now, these particular contacts (VCARD 3.0) get messed up by SailfishOS' CardDAV. There are two issues:

1. Say there's a contact named Tony. He has no surname, so his name field looks like this N:;;;; (both FN and NICKNAME say Tony). After syncing the contact to SFOS it will soon be displayed as ;Tony;;;.
This looks like some sort of parsing bug. Editing the entry and removing the semicolons seems to work but it I have seen it also duplicating the ;Tony;;; part, leading to Name fields looking like this: \;Tony\;\;\;;Tony;;;.
Update: VCard 4.0 seems not to be affected
.

2. The adress book uses categories for grouping. Although those categories do not show up in the SFOS contacts app (not yet supported?), they are parsed once a contact is edited on the phone. If the contacts category has an Umlaut, say ö, SFOS turns it into some unreadable character (displayed as À + an unknown-character box). I can not fix it other than deleting the contact.
This wrongly encoded character completely knocks out Thunderbird/CardDAV (makes the CPU go haywire) _and_ prevents Nextcloud from parsing the contacts at all!
This looks like Unicode is not correctly implemented in the parser.
Update: Happens independently of VCard version

In combination with 1., 2. is very annoying since removing the semicolons from the contact will always result in a corrupted contact

Update:
VCard 4.0 seems not to be affected by 1.
2. Happens independently of VCard version