| Summary: | Support vcard 4 - RFC 6350 | ||
|---|---|---|---|
| Product: | [Applications] kaddressbook | Reporter: | Samir Nassar <samir> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | bberberov+kde, bernhard+kde, ict, kde-bugzilla, montel, psychonaut, tokoe |
| Priority: | NOR | ||
| Version: | 5.23.3 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Attachments: | vCard 4.0 conformant VCF file | ||
|
Description
Samir Nassar
2014-07-24 07:47:35 UTC
In 4.14 we have vcard4.0 support. Not sure that it support IMPP I need to look at. I already need a program which generate vcard4.0 to compare it. Do you know a program which does it ? I don't know of a program myself, but I'm happy to create a vcard file that has all the items of RFC 6350 if that helps. We need to have a program which create a vcard. By hand we can create error etc. There is this PHP library: http://sabre.io/vobject/ which has RFC 6350 conformance. Created attachment 87933 [details] vCard 4.0 conformant VCF file This VCF file is RFC 6350 conformant according to vobject. http://sabre.io/vobject Thanks. I will improve it and test vcard4 support in kaddressbook. Just to add info about progress: I added : - KIND - GENDER - GEO (vcard4.0 format) - LANG - ANNIVERSARY - IMPP (in progress) I continue my vcard4.0 improvment. I added Member too. Just for info: Impp support works now. I fixed CalendarUrl too just for info Impp is supporting but not used by default for the moment. For info I fixed support for "LABEL" in address in vcard4 I continue. I hope a days that it will free bugs :) Is this a tracking bug for all vCard 4.0 incompatibilities? That is, should I report further incompatibilities as comments to this issue, or should I file them as separate bugs and ask that they be linked to this one? (My account here doesn't seem to allow me to set the Depends on/Blocks fields.) When exporting vCards in the 4.0 format, images are exported in the 3.0 format. Actual results: PHOTO;ENCODING=b;TYPE=JPEG:[base64-data] or LOGO;ENCODING=b;TYPE=jpeg:[base64-data] Expected results: PHOTO:data:image/jpeg;base64,[base64-data] or LOGO:data:image/jpeg;base64,[base64-data] This could be affecting "KEY" as well, but I don't have it set up. OS: OpenSUSE Tumbleweed Version: KAddressBook 5.5.2 Do you want a separate bug for this? If you would point me to where in the code this could be, I can try to figure out how to fix this. Thanks. *** This bug has been confirmed by popular vote. *** (In reply to Boian Berberov from comment #14) > When exporting vCards in the 4.0 format, images are exported in the 3.0 > format. > > Actual results: > PHOTO;ENCODING=b;TYPE=JPEG:[base64-data] > or > LOGO;ENCODING=b;TYPE=jpeg:[base64-data] > > Expected results: > PHOTO:data:image/jpeg;base64,[base64-data] > or > LOGO:data:image/jpeg;base64,[base64-data] > > This could be affecting "KEY" as well, but I don't have it set up. > > OS: OpenSUSE Tumbleweed > Version: KAddressBook 5.5.2 > > Do you want a separate bug for this? > > If you would point me to where in the code this could be, I can try to > figure out how to fix this. Thanks. Did anything further happen on that? The export/import from vCards in format 4.0 is still broken. Are there any plans to expand the user interface? Many properties cannot be maintained. |