Re: Evo2 <-> Siemens S55

On Fri, 2004-12-24 at 11:57, Matthias Bläsing wrote:
> 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.

Yes a internal standard should be defined, so that we can sync vcard3.0
<-> intenal format <-> vcard2.1

The problem with evo2 is also that it can only produce 3.0 vcards. When
you request 2.1 cards from evo it just says "not implemented yet"

> 
> Thanks 
> 
> Matthias



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt