Bug 317570 - Vcard 4.0 and xcard not implement in kabc:Adresses
Summary: Vcard 4.0 and xcard not implement in kabc:Adresses
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kdepimlibs
Classification: Applications
Component: kabc (show other bugs)
Version: unspecified
Platform: Other Other
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 317647 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-03-29 22:15 UTC by mparchet
Modified: 2017-01-07 21:26 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mparchet 2013-03-29 22:15:49 UTC
Hello,

I need to use the RELATED and XML function only available with vcard 4.0 format. I'm also interested  to add, in a vcard or xcard the custom property and attribute.

But it  seems that kdepimlib 4.9 or 4.10 only implement the Vcard 2.1 and 3.0  format versions.

When do you think you will implement the vcard 4.0 format ?

Could I already use this format by following the vcard 4.0 specification OR the Xcard format and send it to database throw akonadi ?

Thanks for your support

Best regards

Battant

Reproducible: Always

Steps to Reproduce:
1.See kabc:vcardtools.cpp 4.9.5
2.
3.
Comment 1 mparchet 2013-03-30 13:53:55 UTC
Was this bug already treated in the past ?

Tanks for information.

Best regards

mBattant
Comment 2 Laurent Montel 2013-04-01 10:12:28 UTC
*** Bug 317647 has been marked as a duplicate of this bug. ***
Comment 3 mparchet 2013-04-01 11:45:43 UTC
Hello,

Could you confirm this bug ?

Best regards

mparchet
Comment 4 Denis Kurz 2016-09-24 20:56:21 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kdepim (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 5 Denis Kurz 2017-01-07 21:26:58 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.