Release notes for version 2020.1.18.0.
Added partial support for the vCard 4.0 specification (RFC 6350). See the Specifications Compliance topic for information on features that have not been implemented. The following changes were made to support it. Some of these are breaking changes.
Added support for the PID property parameter.
Added support for the ANNIVERSARY, CLIENTPIDMAP, GENDER, KIND, MEMBER, and RELATED properties.
Added support for the CALSCALE parameter to the BDAY property.
Added support for URI prefixes on the GEO and TEL property values and URI encoding prefixes on binary values in the PHOTO, LOGO, and SOUND properties.
Added support for the GEO, LABEL, and TZ parameters on the ADR property.
AddressTypes.Default was removed as most of its options were removed for vCard 4.0.
Added Text and TextPhone to the PhoneTypes enumeration for vCard 4.0.
The PREF value of the TYPE parameter on the ADR, EMAIL, and TEL properties has changed. It now indicates the preferred order when multiple values are specified using a positive integer value between 1 and 100. This can be useful for ranking multiple values. For example, when providing several phone number contacts, they can be ranked in order of most preferred to least preferred.
When a vCard 4.0 file is saved:
The CONTEXT and CHARSET parameters are not used by vCard 4.0 and will not be saved. The CHARSET parameter is no longer required as the vCard 4.0 format only supports one character set (UTF-8).
When the vCard address property (ADR) is saved, the INTL, DOM, POSTAL, and PARCEL address types will be ignored if saved in the vCard 4.0 format.
The NAME (MIME), MAILER, LABEL, and CLASS properties are not saved as they are not part of the vCard 4.0 specification.
The SORT-STRING property is not saved as it has been replaced by a SORT-AS parameter on the N and ORG properties in vCard 4.0 files.