Re: [SyncEvolution] uri + binary PHOTO values (was: Re: [os-libsynthesis] field merging + parameters)
Hi Patrick,
On Jul 22, 2011, at 15:00 , Patrick Ohly wrote:
I couldn't think of cases where avoiding binary encoding might
have a
negative effect, but you are right, it is not according to spec and it
makes sense to not change existing behavior.
Although I guess many clients would bail out when encountering a PHOTO (non-URI type) with
non-B64 content, I can't imagine photo data possibly be ASCII so I admit this cannot
happen.
But that's now probably *my* paranoia - if it is called "B64" it should do
B64 or some day I will spend hours debugging a case when I have long forgotten about this
special feature and wondering why the hell my test data "foobar" is not coming
out as B64 :-)
Best Regards,
Lukas Zeller, plan44.ch
luz(a)plan44.ch - www.plan44.ch