Ok then, I did some further testing:
1. prepared two pictures, 1 jpeg 1 png 2. added one address entry with the jpeg contact photo 3. added one address entry with png contact photo client was CardDAVMate 0.13.1 browser was Firefox 43.0
Result:
for the jpeg dataset:
BEGIN:VCARD VERSION:3.0 UID:x10h9kx8-upx3-td85-lvr3-4560vcvafvv2 N:Aa;Jpeg;;; FN:Aa Jpeg REV:20151223T075141Z PHOTO;ENCODING=b;TYPE=png:data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAA [many more lines to follow here]
for the png dataset:
BEGIN:VCARD VERSION:3.0 UID:2q2cq44l-qw5t-caqn-s62a-ke657xr0jo9a N:Aa;Png;;; FN:Aa Png REV:20151223T075639Z PHOTO;ENCODING=b;TYPE=png:data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAA [may more lines to follow here...]
Both vcf files have almost the same size.
So CardDAVMate seems to convert the jpeg picture into png. So far so good. Unfortunately, some other clients do not show up the pictures in the address book after syncing. E.g. android smart phone with carddavsync and thunderbird with SOGo Connector. Both clients worked fine until some weeks (months?) ago. In CardDAVMate both pictures show up just fine!
Any ideas?
Cheers,
Gerald
Am 22.12.2015 um 10:34 schrieb Johan Vromans:
On Tue, 22 Dec 2015 09:42:16 +0100 Gerald Rausch rausch@web-rausch.de wrote:
This is part of the 'original' vcard dataset
PHOTO;TYPE=jpeg;ENCODING=b:iVBORw0KGgoAAAANSUhEUgAAAPYAAAESCAYAAAD[...]
So it says it's a JPEG, but it is really a PNG.
When I edit this entry (leave the contact photo unchanged)
What client? If CardDAVMate, what browser?
this is what happens to the photo:
PHOTO;ENCODING=b;TYPE=png:data:image/png;base64,iVBORw0KGgoAAAANSU[...]
The photo contents looks unmodified, but now it is (correctly!) registered as a PNG.
But I assume the photo does not get lost, as it is in my case?
-- Johan