On Fri, 2014-04-04 at 05:28 -0500, anuj chauhan wrote: > Hi Patrick, > > > I created a photo field as mentioned > on https://tools.ietf.org/html/rfc6350#page-30.Below is sample for > that > > > PHOTO:file:///home/droot/evol_store1/photos/Blue hills.jpg. > > > > but when i tracked the outgoing log I found that syncevolution has > converted the string "file:///home/droot/evol_store1/photos/Blue > hills.jpg." into base64 format and sent the url for syncronization,
A full log at loglevel=4 would be useful in cases like this. However, after looking at 04vcard-photo-inlining.xml I have a hunch: you don't specify VALUE=uri explicitly, and the script checks for that. That follows http://www.ietf.org/rfc/rfc2426.txt which says "The default is binary value." You used vCard 4.0, which is not used or supported by SyncEvolution. vCard 4.0 has a different definition of the PHOTO property (value is always a URI and inline data is represented as a special URI). -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ os-libsynthesis mailing list os-libsynthesis@synthesis.ch http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
