On Di, 2011-05-10 at 15:18 +0100, Ove Kåven wrote: > Den 18. april 2011 10:14, skrev Patrick Ohly: > > Possible answers: > > * Only transcode if it is detected during a sync that photos had > > problems. > > * Hard-code certain profiles, match them to DevInf reported by > > device (based on max item size, for example). > > * Preserve local photo data if transcoding was necessary. > > Is it possible to save the MD5/SHA/whatever of the transcoded image > somewhere, so that it will be possible to check whether the device's > image is still the one from the original transcoding?
That might work, as long as the peer stores a bit-exact copy of the transcoded image. Once it changes something, we are back to the original problem: the checksum will no longer match and we can't decide between "image was intentionally changed" and "ignore unintentional change". I haven't checked what phones do; at least some SyncML servers convert images, as far as I remember. -- 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. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
