Created attachment 47770 [details] Original VCard with 3 phones and IM address Version: unspecified (using KDE 4.4.2) OS: Linux When migrating from Outlook to Kontact svereal fields are mislabeled or missing. First: X-KADDRESSBOOK-X-IMAddress:ICQ: 269739266 should be X-KADDRESSBOOK-X-IMAddress:ICQ: 269739266 So informations get lost (IM Address) and Even when entered and exported it is unusable elsewhere. Second: TEL;WORK;VOICE:731460976 TEL;HOME;VOICE:272767631 TEL;CELL;VOICE:739673971 is not reed as equivalent phones, but rather uneditable Other fields. Even when changed to equivalent fileds - change is not saved. Reproducible: Always Steps to Reproduce: Import an Outlook VCard with filled fields: Mobile, IM-Address Actual Results: Fields URL, IM Address get lost Field VOICE (Mobile, Work, Home) gets mislabeled and could not be edited afterwards. (Change is not saved.) Expected Results: Import fields correctly. Including 2 VCards, one from outlook and the other one exported after filling IM Address from Kontact
Created attachment 47771 [details] Exported VCArd from kontact (IM Address is filled out)
"Fields URL, IM Address get lost" Pardon, my mistake only IM Address get lost.
"X-KADDRESSBOOK-X-IMAddress:ICQ: 269739266 should be X-KADDRESSBOOK-X-IMAddress:ICQ: 269739266" Again my mistake I am sorry misclick: X-KADDRESSBOOK-X-IMAddress:ICQ: 269739266 should be X-MS-IMADDRESS:ICQ: 269739266
Hej Martin, unfortunately the vCard standard in version 3.0 has no field for IM defined, therefor every implementation uses its own custom 'X-' fields, that are not supposed to be supported by different implementations (according to the standard). Outlook decided to use one key, we decided to use another, Evolution uses yet another one... With the new vCard standard that is currently in development those issues will hopefully be fixed, but until then we won't adapt our parser just because somebody else used something else. Since these keys can easily be replaced with a simple perl/awk script we see no urgent reason to add the burden on our vCard parser/synthesizer to do the conversion. Ciao, Tobias
RFC4770 [1] defines fields for IM like: IMPP;TYPE=personal,pref:xmpp:alice@example.com The protocol is defined according to the URI. There are several protocols mentioned as examples: "sip", "xmpp" (Jabber/XMPP), "irc", "ymsgr", "msn", "aim", "im" or "pres" (for CPIM or CPP gateway) For gadu-gadu, you can use "gg"; for sms, "sms"; for skype, "callto" or "skype" But GroupWise, ICQ and Meanwhile doesn't seem to have a URI defined, so you may need to extend it. [1] http://tools.ietf.org/html/rfc4770
If kaddressbook supported import/export of vcard 4 (RFC 6350) along with ownCloud this would resolve the issue. https://bugs.kde.org/show_bug.cgi?id=337759