Am Do, den 23.12.2004 schrieb Christoph Lukas um 21:18: > Same here. Might the vcard version be a problem? I saw > > Body: BEGIN:VCARD > VERSION:2.1 > > when syncing S55=>Evo > > and > > Body: BEGIN:VCARD > VERSION:3.0 > > when syncing Evo=>S55. Might it be possible that the S55 does not > understand Vcard version 3?
That might be a good starting point. It would correlate quite well with the fact, that each end of the pair S55(via IRMC)-Evo2 works very well (tested with the Backup Plugin) individually. So the question is - what can we do? A compatibility layer in IRMC or in Evo2? One Option is to convert vcards comming from Evo2 from Version 3.0 to 2.1 or covert vcards from IRMC the other way round. For my part I would be happy with a hack, making my S55 work with Evo2. I found a perl script for converting vcard 3.0 to 2.1, but it seemed a little bit to easy. AND what's makes it worse is, that I not a skilled C-Programmer (meaning I only used C for _some_ homework for my system programming lecture at university). One question remains. Isn't there a internal standard format - or at least shouldn't one be agreed on? I can't think, that the S55 is the only device not understanding Vcard 3.0 and Evo2 won't be the only application providing Vcard 3.0. Thanks Matthias -- "With the first link, the chain is forged. The first speech censored, the first thought forbidden, the first freedom denied, chains us all irrevocably." Captain Picard, quoting Judge Aaron Satie (Enterprise TNG - The Drumhead) ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Multisync-users mailing list Multisync-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/multisync-users
