Bug 231004 - vcard embedded photos: Option to use "ENCODING=BASE64" instead of "ENCODING=b"
Summary: vcard embedded photos: Option to use "ENCODING=BASE64" instead of "ENCODING=b"
Status: RESOLVED INTENTIONAL
Alias: None
Product: kaddressbook
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-16 18:49 UTC by wuselwu
Modified: 2010-03-16 20:18 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description wuselwu 2010-03-16 18:49:07 UTC
Version:            (using KDE 4.4.1)
Installed from:    openSUSE RPMs

Currently Kaddressbook saves vcards with embedded photos with the following line:
PHOTO;ENCODING=b;TYPE=image/jpeg...

For years now I've tried to sync such vcards with my mobile phones (Nokia, Symbian) and always got errors with this setting.

Now I found out that you can synonymous use the following line:
PHOTO;ENCODING=BASE64;TYPE=image/jpeg...
After changing this line manually in all my contacts, my phone finally accepts the vcards with embedded photos!

It would be great to have an option for that in the export function.
Comment 1 wuselwu 2010-03-16 20:10:58 UTC
Another workaround for broken vcard handys of some Symbian mobile phones (e.g. my Nokia E51): If the embedded picture isn't the last entry in the vcard file, all following entries are discarded by this phone. Maybe Kaddressbook could have a legacy/workaround option in its export functionality in order to fix this problem, and the one described in my first post?

BTW, I'm talking  about exporting as vcard 2.1, as vcard 3.0 also has problems with German umlauts in my phone.
Comment 2 Tobias Koenig 2010-03-16 20:18:26 UTC
Hej Lars,

I don't want to discourage you but honestly I don't feel like implementing
lots of hacks into KAddressBook just to work around broken hardware of
phone vendors...
This should be done by real synchronization software which knows the bugs of
the device to synchronize with and can adopt the data format according.

Ciao,
Tobias