Closed ghost closed 11 years ago
The instant messaging properties has been implemented according to RFC 4770 vCard Extensions for Instant Messaging which will also be a part of the vCard 4 specification. Supporting the X-* equivalents has very low priority.
Support for NICKNAME and TITLE is implemented for ownCloud 5.
ANNIVERSARY and GENDER are not standard properties and should be 'X-' prefixed.
Supporting non-standard properties is not on top of the todo list I'm afraid, but I'll keep this report open for discussion on the most wanted additions.
Multiple URLs would be really nice. I often have URL;TYPE=HOME:xxxx URL;TYPE=WORK:yyyy URL;TYPE=WORK:zzzz etc.
And I'd also like to see a (compatible) way to enter one or two anniversary dates and the date of the saint's day. Maybe implemented as multiple/named "birthdays"? Thanks so much, Andy.
Multiple URLs would be really nice.
It is implemented for ownCloud 5.0.
+1 for the ANNIVERSARY
The instant messaging properties has been implemented according to RFC 4770 vCard Extensions for Instant Messaging which will also be a part of the vCard 4 specification.
The RFC 4770 is dated from August 2007 and meanwhile obsoleted by RFC 6350 vCard Format Specification (dated August 2011) which contains ANNIVERSARY as a vCard 4 property - might be worth a second thought....
I sync the OC contacts with my mobile phone (via CardDAV) - and whenever I edit a contact with anniversary on ownCloud, the anniversary disappears with next sync. Not a surprise actually, but definitely an undesired consequence. Manually maintaining anniversaries of existing contacts in the calendar is not an option.
Currently only version 3.0 is supported, but I implement some version 4.0 stuff.
and whenever I edit a contact with anniversary on ownCloud, the anniversary disappears with next sync.
That should definitely not happen. The sync process must be non-destructive, except updating to v. 3.0 if needed. Please file a separate issue about that. One other exception is if a line in the vCard is too malformed for Sabre VObject to parse it, the line will be skipped. Otherwise the vCard would be rejected all together. When filing the issue please attach an anonymized version of a vCard with an ANNIVERSARY property.
That should definitely not happen. The sync process must be non-destructive, except updating to v. 3.0 if needed. Please file a separate issue about that.
I will, but first I will go a bit deeper into the details. Thx for the clarification.
Can you please add support for additional contact fields like ANNIVERSARY, GENDER. IMPP, NICKNAME, ROLE (= TITLE?), X-ASSISTANT, X-MANAGER, X-SPOUSE, X-AIM, X-ICQ , X-JABBER, X-MSN, X-YAHOO, X-TWITTER, X-SKYPE, X-SKYPE-USERNAME, X-GADUGADU, X-MS-IMADDRESS and CHILDS (i dont know the correct name of this). Is this possible?