Hello Stefano! Good to see you here :-)
On Tue, 2009-07-28 at 10:19 +0100, Stefano Maffulli wrote: > Hi > > On Mon, 2009-07-27 at 14:08 +0200, Patrick Ohly wrote: > > and there's one open Funambol issue. > > which issue is still pending? http://bugzilla.moblin.org/show_bug.cgi?id=4598 Funambol: Company phone property will lost in syncing addressbook with funambol The server sends TEL;TYPE="X-EVOLUTION-COMPANY" to the client, which is not something that is currently recognized. As Yongsheng said in the bug report, this is an Evolution extension for "company phone number", in contrast to the normal work or "business phone number". There are several issues related to it, ranging from parsing problems to the server not understanding the TYPE. I think it would be best if the server used TYPE=WORK instead of TYPE="X-EVOLUTION-COMPANY". > Also, against which server did you test > it? Is this issue still present on the v8 Release Candidate? We testing with myFUNAMBOL. > The RC > files are on http://forge.ow2.org/project/showfiles.php?group_id=96 and > the GA is expected in days now. I downloaded that and grepped for X-EVOLUTION-COMPANY. Ah, it is in config/com/funambol/server/engine/pipeline/phones-support/bsh/SyncEvolutionin.bsh: /** * Remaps the following properties: * TEL;X-EVOLUTION-UI-SLOT=;TYPE=PREF into TEL;VOICE * TEL;X-EVOLUTION-UI-SLOT=;TYPE=VOICE into TEL;PREF;VOICE * TEL;X-EVOLUTION-UI-SLOT=;TYPE=\"X-EVOLUTION-COMPANY\" into TEL;WORK;PREF * @param data the data to process * * @return the modified data */ void preProcessContact(Item i) { data = i.data.data; data = replaceInProperty(data, "TEL;X-EVOLUTION-UI-SLOT=\\d;TYPE=PREF" , "TEL;VOICE" ); data = replaceInProperty(data, "TEL;X-EVOLUTION-UI-SLOT=\\d;TYPE=VOICE" , "TEL;PREF;VOICE"); data = replaceInProperty(data, "TEL;X-EVOLUTION-UI-SLOT=\\d;TYPE=\"X-EVOLUTION-COMPANY\"", "TEL;WORK;PREF" ); i.data.data = data; } I remember that we had a discussion once about Funambol putting TEL;PREF into the "other" phone number in the web and using TEL;OTHER as the main phone number. I still think that this reverses the logic, but apparently it was necessary for some other clients: http://thread.gmane.org/gmane.comp.mobile.funambol.devel/3210 Is the Synclet mapping bidirectional, in other words, does it work for incoming and outgoing items? I think the mapping for X-EVOLUTION-COMPANY should be removed. I don't remember whether we discussed this in the past and a mail search didn't bring it up. Can you ask the myFUNAMBOL developers/admins about this? Filing bug reports or mailing the lists often doesn't get prompt (or any) reply. For example, the "lost ACTION" email hasn't drawn any response. We've got a workaround though, so that isn't relevant anymore, except perhaps for other clients. > If it helps you to know, myFUNAMBOL will > be migrated to v8 not sooner than the end of August. I definitely hope that we'll release 0.9 sooner than that ;-) So let's focus on the current v7 release. We can retest and update test/README.funambol and the corresponding Compatibility page entry once v8 is roled out. -- 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
