On Di, 2011-03-01 at 16:19 +0000, Patrick Ohly wrote: > On Di, 2011-03-01 at 15:54 +0000, Thomas Pequet wrote: > > In fact, it is normal, besause the "Rx-Pref" and "Tx-Pref" are > > "text/v-card" 2.1 and not "text/vcard" 3.0. > > So Memotoo send only: > > > > <CTCap> > > <CTType>text/x-vcard</CTType> > > <VerCT>2.1</VerCT> > > > > If you set the pref Rx and Tx to 3.0, Memotoo will send the field > > Nickname. > > I thought we had arrived at a solution where vCard 3.0 is used > automatically when SyncEvolution is detected, but you are right. Making > vCard 3.0 the preferred format will require all SyncEvolution to update > their configs... unless I change the default. Let me try that and see > whether it breaks some other server.
It does (for example, Mobical). Therefore I have reverted to vCard 2.1 as the default sync format and implemented a different approach for MemoToo: commit da7f503bee76a48d670ca2114dc83bc7d774d04c Author: Patrick Ohly <[email protected]> Date: Wed Mar 2 11:05:18 2011 +0100 Memotoo: use vCard 3.0 When SyncEvolution prefers vCard 3.0, additional properties like NICKNAME work with Memotoo. This patch a) makes that the default syncFormat in the Memotoo template and b) automatically sets it in the "addressbook" source of all migrated configs which sync with Memotoo (detected based on the syncURL). The automatic config rewriting is possible because users upgrading from the previous stable SyncEvolution release need to migrate their configs anyway. Normally SyncEvolution does not modify configs like this. -- 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. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
