Re: [os-libsynthesis] sending photo to Nokia phone (N97 mini): wrong CTCap
On Thu, 2010-08-26 at 23:00 +0100, Lukas Zeller wrote: it's a known bug in many Nokia phones that they have a maxSize of 255 on all fields, including the PHOTO. And yes, there is a remoterule option called ignoredevinfmaxsize for that. It applies to all fields, however I agree that those constant 255 maxsizes are probably meaningless anyway. Ah, excellent. I was sure there would be something, and I wasn't disappointed ;-) Speaking of CtCap, do you happen to know what Nokia's involvement was in the definition of that part of the spec? Or speaking more generally, what was the desired usage of CtCap? I've just been in another discussion around that, where the Synthesis use of CtCap to determine unsupported properties was questioned. One interpretation of CtCap is limitations for some properties. In that interpretation, unlisted properties might still be supported. The other interpretation is that CtCap has to be complete and accurate, and thus anything not covered by it (value too long, unknown property) is not stored by the device. This is the interpretation used by Synthesis. FWIW, it sounds more plausible to me. But is there anything in the standard which supports one or the other interpretation? Or perhaps it was part of meeting minutes? -- 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
Re: [os-libsynthesis] sending photo to Nokia phone (N97 mini): wrong CTCap
Hi Patrick, On Aug 30, 2010, at 10:43 , Patrick Ohly wrote: Speaking of CtCap, do you happen to know what Nokia's involvement was in the definition of that part of the spec? Or speaking more generally, what was the desired usage of CtCap? I've just been in another discussion around that, where the Synthesis use of CtCap to determine unsupported properties was questioned. One interpretation of CtCap is limitations for some properties. In that interpretation, unlisted properties might still be supported. The other interpretation is that CtCap has to be complete and accurate, and thus anything not covered by it (value too long, unknown property) is not stored by the device. This is the interpretation used by Synthesis. FWIW, it sounds more plausible to me. The real world devices that most prominently and strictly supported our interpretation were Nokia's. We had a lot of trouble of getting all data out of them without entirely omitting CTCap in the beginning, until we found that not only all properties needed to be listed (that was the case already in very early versions of our server), but also the complete list of possible property parameters. For example, a Nokia phone would not send any telephone number unless the CTCap had not only TEL but also the possible property parameters WORK, HOME, CELL... And because their clients were for a long time pretty much the only ones looking at CTCap at all apart from ours, I'd at least say that this interpretation is a de facto standard. But I have no insight into the involvement of Nokia in that part of the specs. But is there anything in the standard which supports one or the other interpretation? If there is, I am not aware of it. Or perhaps it was part of meeting minutes? Maybe, I don't know. Lukas Zeller (l...@synthesis.ch) - Synthesis AG, SyncML Solutions Sustainable Software Concepts i...@synthesis.ch, http://www.synthesis.ch ___ os-libsynthesis mailing list os-libsynthesis@synthesis.ch http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
Re: [os-libsynthesis] sending photo to Nokia phone (N97 mini): wrong CTCap
Hi Patrick, it's a known bug in many Nokia phones that they have a maxSize of 255 on all fields, including the PHOTO. And yes, there is a remoterule option called ignoredevinfmaxsize for that. It applies to all fields, however I agree that those constant 255 maxsizes are probably meaningless anyway. Lukas On Aug 26, 2010, at 17:24 , Patrick Ohly wrote: Hello! I'm investigating why a photo sent to a Nokia device does not show properly on the device. It was originally reported for a 5800 (http://bugs.meego.com/show_bug.cgi?id=5860); I can also reproduce it with a N97 mini. One problem is that the device lies about its capabilities. CTCap contains 256 as maximum length for PHOTO. When encoding, the Synthesis library dutifully obliges and truncates the field. The device clearly is capable of handling larger photos - the photo was originally attached to the contact *on* the device itself and then copied to the server. Is there a remote rule that I can use to ignore the length limitation of the PHOTO property? Should I ignore the whole CTCap, as it is clearly not based on reality? I think there is an option for that, but won't that have undesirable effects like not preserving local extensions that are really not supported by the phone? Another problem might be the TYPE. Evolution doesn't set JPEG by itself. We may have to add that to the outgoing PHOTO. -- 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 Lukas Zeller (l...@synthesis.ch) - Synthesis AG, SyncML Solutions Sustainable Software Concepts i...@synthesis.ch, http://www.synthesis.ch ___ os-libsynthesis mailing list os-libsynthesis@synthesis.ch http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
