On Wed, 2009-10-14 at 13:37 +0100, Lukas Zeller wrote: > I haven't come across phones that crash on b64 folding spaces as > mobical apparently did. Can we find out more about which ones this > applies to? I know of phones that crash on any folding (Moto V3 and > Razr), but for these we have <nocontentfolding>.
Folding seems to be more trouble than it's worth, so SyncEvolution always disables it. > On the parsing side, the the patch I added today (see previous email) > will work with or without that empty line. I've enabled the PHOTO property comparison in the automated testing for Mobical. It was turned off because when interoperability was tested, the server seemed to modify our test photos, but send them back without triggering this problem (according to our README.mobical). I haven't done that testing myself, so I assume that something has changed since then. Without your patch, the testing finds that the PHOTO is truncated. With the patch, it gets a bit too long ;-} qGIlf17k6Bb/Ae0cnahfg6KuAAAAAElFTkSuQ qGIlf17k6Bb/Ae0cnahfg6KuAAAAAElFTkSuQ mCC | mCCENDVCARD URL:http://john.doe.com URL:http://john.doe.com This is something which happens on the way to the server. What we send is: NOTE:image in PNG format PHOTO;ENCODING=BASE64:iVBORw...uQmCC END:VCARD Note that folding is turned off, so it is really one long line. I shortened it by replacing the middle with dots. Shouldn't there be a blank line after the PHOTO property, to comply with the BASE64 encoding rules? -- 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 [email protected] http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
