Revision history [back]

Hello together,

maybe an issue with the Sailfish Contacts App that causes problems when syncing via CalDAV/CardDAV.

Description of the problem:

The Contacts App does not use the standardized birthday-format (YYYYMMDD) when transmitting contacts via CardDAV. Instead of that, it uses some unstandardized YYYY-MM-DD system with hyphens as separators. Because of that, OwnCloud, Nextcloud, Thunderbird and many other CardDAV/CalDAV-Services can not recognize the correct dates of birthdays from persons in the phone address book and therefore leave those fields empty.

Standardized format: YYYYMMDD ⇨ seamless integration into different services via CardDAV/CalDAV

Jolla-format: YYYY-MM-DD ⇨ problems when syncing to OwnCloud/Nextcloud/Thunderbird, etc.

Did anyone experience the same behavior?

You can test this by yourself by simply exporting your contacts into a *.vcf-file. The nowadays *.vcf-standard is strictly YYYYMMDD, but Sailfish produces YYYY-MM-DD (see in file).

Could you change this please?

Thank you very much!

Hello together,

maybe an issue with the Sailfish Contacts App that causes problems when syncing via CalDAV/CardDAV.CalDAV/CardDAV.

Description of the problem:issue

The Contacts App does not use the standardized birthday-format date-format (YYYYMMDD) for birthdays/dying days when transmitting contacts via CardDAV. Instead of that, it uses some unstandardized YYYY-MM-DD system with hyphens as separators. Because of that, OwnCloud, Nextcloud, Thunderbird and many other CardDAV/CalDAV-Services can not recognize the correct dates of birthdays from persons in the phone address book and therefore leave those fields empty.

Did anyone experience the same behavior?

You can test this by yourself by simply exporting your contacts into a *.vcf-file. The nowadays *.vcf-standard is strictly YYYYMMDD, but Sailfish produces YYYY-MM-DD (see in file).

Could you change this please?

Thank you very much!

Hello together,

maybe probably an issue with the Sailfish Contacts App that causes problems when syncing via CalDAV/CardDAV.

Description of the issue

The Contacts App does not use the standardized date-format (YYYYMMDD) for birthdays/dying days birthdays/anniversaries when transmitting contacts via CardDAV. Instead of that, it uses some unstandardized YYYY-MM-DD system format with hyphens as separators. Because of that, that issue, OwnCloud, Nextcloud, Thunderbird and many other CardDAV/CalDAV-Services can not recognize the correct dates of birthdays birthdays/anniversaries from persons in the phone address book and therefore leave those fields empty.

1. Jolla-format: YYYY-MM-DD ⇨ problems when syncing to OwnCloud/Nextcloud/Thunderbird, etc.

2. Standardized format: YYYYMMDD ⇨ seamless integration into different services via CardDAV/CalDAV

Did anyone experience the same behavior? behavior?

You can test this by yourself by simply exporting your contacts into a *.vcf-file. The nowadays *.vcf-standard is strictly YYYYMMDD, but Sailfish produces YYYY-MM-DD (see in file).

Even the official vCard-rules desire to write dates as YYYYMMDD (e.g. BDAY:19700310).

Could you change this in Sailfish, please?

Thank you very much!

Hello together,

probably an issue with the Sailfish Contacts App that causes problems when syncing via CalDAV/CardDAV.

Description of the issue

The Contacts App does not use the standardized date-format (YYYYMMDD) for birthdays/anniversaries when transmitting contacts via CardDAV. Instead of that, it uses some unstandardized YYYY-MM-DD format with hyphens as separators. Because of that issue, OwnCloud, Nextcloud, Thunderbird and many other CardDAV/CalDAV-Services can not recognize the correct dates of birthdays/anniversaries from persons in the phone address book and therefore leave those fields empty.

1. Jolla-format: YYYY-MM-DD ⇨ problems when syncing to OwnCloud/Nextcloud/Thunderbird, etc.

2. Standardized format: YYYYMMDD ⇨ seamless integration into different services via CardDAV/CalDAV

Did anyone experience the same behavior?

You can test this by yourself by simply exporting your contacts into a *.vcf-file. The nowadays *.vcf-standard is strictly YYYYMMDD, but Sailfish produces YYYY-MM-DD (see in file).

Even the official vCard-rules desire to write dates as YYYYMMDD (e.g. BDAY:19700310).

Could you change this in Sailfish, please?

Thank you very much!

Hello together,

probably an issue with the Sailfish Contacts App that causes problems when syncing via CalDAV/CardDAV.

Description of the issue

The Contacts App does not use the standardized date-format (YYYYMMDD) for birthdays/anniversaries when transmitting contacts via CardDAV. Instead of that, it uses some unstandardized YYYY-MM-DD format with hyphens as separators. Because of that issue, OwnCloud, Nextcloud, Thunderbird and many other CardDAV/CalDAV-Services can not recognize the correct dates of birthdays/anniversaries from persons in the phone address book and therefore leave those fields empty.

1. Jolla-format: YYYY-MM-DD ⇨ problems when syncing to OwnCloud/Nextcloud/Thunderbird, etc.

2. Standardized format: YYYYMMDD ⇨ seamless integration into different services via CardDAV/CalDAV

Did anyone experience the same behavior?

You can test this by yourself by simply exporting your contacts into a *.vcf-file. The nowadays *.vcf-standard is strictly YYYYMMDD, but Sailfish produces YYYY-MM-DD (see in file).

Even the official vCard-rules desire to write dates as YYYYMMDD (e.g. BDAY:19700310).

Could you change this in Sailfish, please?

Thank you very much!

Hello together,

probably an issue with the Sailfish Contacts App that causes problems when syncing via CalDAV/CardDAV.

Description of the issue

The Contacts App does not use the standardized date-format (YYYYMMDD) for birthdays/anniversaries when transmitting contacts via CardDAV. Instead of that, it uses some unstandardized YYYY-MM-DD format with hyphens as separators. Because of that issue, OwnCloud, Nextcloud, Thunderbird and many other CardDAV/CalDAV-Services can not recognize the correct dates of birthdays/anniversaries from persons in the phone address book and therefore leave those fields empty.

1. Jolla-format: YYYY-MM-DD ⇨ problems when syncing to OwnCloud/Nextcloud/Thunderbird, etc.

2. Standardized format: YYYYMMDD ⇨ seamless integration into different services via CardDAV/CalDAV

Did anyone experience the same behavior?

You can test this by yourself by simply exporting your contacts into a *.vcf-file. The nowadays *.vcf-standard is strictly YYYYMMDD, but Sailfish produces YYYY-MM-DD (see in file).

Even the official vCard-rules desire to write dates as YYYYMMDD (e.g. BDAY:19700310).

Could you change this in Sailfish, Sailfish to the worlwide harmonized YYYYMMDD-system, please?

Thank you very much!

Hello together,

probably an issue with the Sailfish Contacts App that causes problems when syncing via CalDAV/CardDAV.

Description of the issue

The Contacts App does not use the standardized date-format (YYYYMMDDYYYYMMDD) for birthdays/anniversaries when transmitting contacts via CardDAV. Instead of that, it uses some unstandardized YYYY-MM-DD format with hyphens as separators. Because of that issue, OwnCloud, Nextcloud, Thunderbird and many other CardDAV/CalDAV-Services can not recognize the correct dates of birthdays/anniversaries from persons in the phone address book and therefore leave those fields empty.

1. Jolla-format: YYYY-MM-DD ⇨ problems when syncing to OwnCloud/Nextcloud/Thunderbird, etc.

2. Standardized format: YYYYMMDDYYYYMMDD ⇨ seamless integration into different services via CardDAV/CalDAV

Did anyone experience the same behavior?

You can test this by yourself by simply exporting your contacts into a *.vcf-file. The nowadays *.vcf-standard is strictly YYYYMMDDYYYYMMDD, but Sailfish produces YYYY-MM-DD nevertheless (see in file).

Even the official vCard-rules vCard-rules as well as the international RFC 6350 standard desire to write dates as YYYYMMDD in the YYYYMMDD-format (e.g. BDAY:19700310).

Could you change this in Sailfish to the worlwide harmonized YYYYMMDD-system, YYYYMMDD-system, please?

Thank you very much!

Hello together,

probably I found an issue with the Sailfish Contacts Contacts App that causes problems when syncing via CalDAV/CardDAV.

Description of the issue

The Contacts Contacts App does not use the standardized date-format (YYYYMMDD) for birthdays/anniversaries when transmitting contacts via CardDAV. Instead of that, it uses some unstandardized YYYY-MM-DD format with hyphens as separators. Because of that issue, OwnCloud, Nextcloud, Thunderbird and many other CardDAV/CalDAV-Services can not recognize the correct dates of birthdays/anniversaries from persons in the phone address book and therefore leave those fields empty.

1. Jolla-format: YYYY-MM-DD ⇨ problems when syncing to OwnCloud/Nextcloud/Thunderbird, etc.

2. Standardized format: YYYYMMDD ⇨ seamless integration into different all services via CardDAV/CalDAV using CardDAV/CalDAV:

Did anyone experience the same behavior?

You can test this by yourself by simply exporting your contacts into a *.vcf-file. The nowadays *.vcf-standard is strictly YYYYMMDD, but Sailfish produces YYYY-MM-DD nevertheless (see in file).

Even the official vCard-rules as well as the international RFC 6350 standard desire to write dates in the YYYYMMDD-format (e.g. BDAY:19700310).

Could you change this in Sailfish to the worlwide harmonized YYYYMMDD-system, please?

Thank you very much!