Hi Jussi, On Feb 17, 2010, at 10:58 , Jussi Kukkonen wrote:
> Jussi Kukkonen wrote: >> Yes, seems to work well now. Everything I could think of adding on the phone >> ends up on the server -- and this is with no showctcapproperties tricks. >> So it seems you may be correct about the X-* types being the problem. > > Patrick informed me that I can copy the default 01vcard-profile.xml into > ~/.config/syncevolution-xml/datatypes/ and modify there: After a quick test > it seems that some extras are allowed but some will disable the whole > property. > > As an example, this is the default TEL property: > [...] >> <parameter name="X-EVOLUTION-UI-SLOT" positional="no" show="yes"> >> <value field="TEL_SLOT"/> >> </parameter> > > Removing the parameter X-EVOLUTION_UI-SLOT is enough to get the phone to send > TEL data: the extra enums don't seem to bother it. You could hide the parameter from the CTCAP (but keeping it active and working for peers that support it) by setting the "show" attribute to "no" instead of removing the entire parameter. Lukas Zeller ([email protected]) - Synthesis AG, SyncML Solutions & Sustainable Software Concepts [email protected], http://www.synthesis.ch _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
