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
